Adjust help for +edit/field.publish on Private PPA to state that it also prevents build dispatch
Bug #690561 reported by
Paul Sladen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Low
|
Colin Watson | ||
Bug Description
https:/
<spm> sladen: ahh. that was subtle. turns out your PPA was disabled from building. effectively. There's a flag that Private PPA's have via the +edit, "Publish"
<spm> and that had been unchecked. and hence, you're top of the queue, but never get built.
<spm> One package has now built, the other is building.
Ideally the text should make it clear that "published" won't actually publish anything (it's a _private_ PPA), but still stop the build system working, prevent any packages getting built, and therefore prevent the user wanting to publish the archive (classic Catch-22).
See also bug #690484.
| tags: | added: p3a ppa trivial ui |
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| affects: | launchpad → soyuz |
| summary: |
Adjust help for +edit/field.publish on Private PPA to state that it also - stops the builddaemons + prevents build dispatch |
Revision history for this message
| Colin Watson (cjwatson) wrote | #1 |
| Changed in launchpad: | |
| assignee: | nobody → Colin Watson (cjwatson) |
| status: | Triaged → Fix Released |
To post a comment you must log in.
This is no longer an issue, but not by changing the UI: rather, private builds are now dispatched without needing to wait for their source to be published.