"All source packages" page empty when distribution doesn't use Launchpad for packaging
Bug #196322 reported by
Matthew Paul Thomas
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Low
|
Edwin Grubbs | ||
Bug Description
<https:/
The page should explain why Nexenta has no packages registered in Launchpad.
Related branches
lp:~edwin-grubbs/launchpad/bug-234051-bug-project-info
- Curtis Hovey (community): Approve (ui)
- Martin Albisetti (community): Approve (ui)
- Barry Warsaw (community): Approve (code ui*)
- Canonical Launchpad Engineering: Pending (code) requested
-
Diff: 258 lines (+44/-124)8 files modifiedlib/canonical/launchpad/icing/style-3-0.css (+0/-4)
lib/lp/bugs/browser/configure.zcml (+2/-2)
lib/lp/bugs/templates/bugtask-macros-listing.pt (+39/-28)
lib/lp/registry/browser/configure.zcml (+0/-7)
lib/lp/registry/browser/distribution.py (+1/-16)
lib/lp/registry/stories/distribution/xx-distribution-all-packages.txt (+0/-40)
lib/lp/registry/templates/distribution-allpackages.pt (+0/-25)
lib/lp/registry/templates/person-portlet-currentfocus.pt (+2/-2)
| Changed in soyuz: | |
| status: | New → Confirmed |
| Changed in soyuz: | |
| importance: | Undecided → Low |
| status: | Confirmed → Triaged |
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #1 |
| affects: | soyuz → launchpad-registry |
| Changed in launchpad-registry: | |
| milestone: | none → 3.1.10 |
| tags: | added: post-3-ui-cleanup |
| Changed in launchpad-registry: | |
| assignee: | nobody → Edwin Grubbs (edwin-grubbs) |
| status: | Triaged → In Progress |
| Changed in launchpad-registry: | |
| milestone: | 3.1.10 → 3.1.11 |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #2 |
| Changed in launchpad-registry: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Edwin Grubbs (edwin-grubbs) wrote Bug 196322 Fix released | #3 |
| Changed in launchpad-registry: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Related to bug 126485.
The page is not linked from anywhere any more, the registry team may consider killing it.