Unable to set name of first PPA created for team/person
Bug #439305 reported by
Cody A.W. Somerville
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Julian Edwards |
Bug Description
The first PPA created for a team/person should not be forced to have the name 'ppa'. It should be settable just like when you create any subsequent PPA.
Related branches
lp://qastaging/~julian-edwards/launchpad/first-ppa-name-bug-439305
- Francis J. Lacoste (community): Approve (release-critical)
- Eleanor Berger: Pending requested
-
Diff: 426 lines9 files modifiedlib/lp/registry/model/person.py (+3/-8)
lib/lp/soyuz/browser/archive.py (+13/-3)
lib/lp/soyuz/doc/archive.txt (+18/-1)
lib/lp/soyuz/interfaces/archive.py (+17/-2)
lib/lp/soyuz/model/archive.py (+14/-1)
lib/lp/soyuz/stories/ppa/xx-copy-packages.txt (+1/-1)
lib/lp/soyuz/stories/ppa/xx-ppa-private-teams.txt (+2/-2)
lib/lp/soyuz/stories/ppa/xx-ppa-workflow.txt (+46/-30)
lib/lp/soyuz/templates/archive-activate.pt (+0/-4)
Changed in soyuz: | |
assignee: | Michael Nelson (michael.nelson) → Julian Edwards (julian-edwards) |
Changed in soyuz: | |
status: | Triaged → In Progress |
Changed in soyuz: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Note to whoever fixes this: We need to fix IPerson.archive first since it depends on the name of the first PPA being "ppa". When that's done the PPA creation form's restriction on the name can be relaxed on the first PPA.