PPA admins can no longer set Archive.private
Bug #1531168 reported by
Shawn Wang
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Critical
|
Colin Watson |
Bug Description
We use launchpadlib to create oem project ppa in ~oem-archive.
launchpad account: lexbuilder.
It worked before.
I'm not sure is it related about the update of lp. http://
It seems it change some of ppa permission.
Error messages https:/
code piece:
ppa = team.createPPA(
name=project,
displayname
description
private=True)
ppa.require_
ppa.authorized_size = 1000*1000
...
ppa.lp_save()
Related branches
lp:~cjwatson/launchpad/ppa-admins-private
- William Grant: Approve (code)
-
Diff: 85 lines (+20/-15)3 files modifiedlib/lp/soyuz/configure.zcml (+4/-6)
lib/lp/soyuz/stories/webservice/xx-archive.txt (+15/-8)
lib/lp/soyuz/tests/test_archive.py (+1/-1)
summary: |
- PPA admins can no longer set Archive.private + PPA admins can no longer set Archive.private and Archive.authorized_size |
summary: |
- PPA admins can no longer set Archive.private and Archive.authorized_size + PPA admins can no longer set Archive.private |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Yes, that revision regressed the ability of launchpad- ppa-self- admins members to change the private flag. That ability is a bit weird, and I didn't realise anyone was relying on it, but it sounds as though we'd better put it back for the time being.