When a binary package is not accepted (e.g. NEW) build page still tries to link to it
Bug #301504 reported by
James Westby
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Medium
|
Michael Nelson | ||
Bug Description
Hi,
Starting from
https:/
and clicking one of the binary package links goes to
https:/
leads to an OOPS (e.g. OOPS-1059EB22)
The binary packages are currently in NEW, and that would seem to be the cause.
Thanks,
James
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #1 |
| Changed in soyuz: | |
| assignee: | nobody → michael.nelson |
| importance: | Undecided → Medium |
| milestone: | none → 2.1.12 |
| status: | New → Triaged |
| Changed in soyuz: | |
| milestone: | 2.1.12 → 2.2.1 |
| Changed in soyuz: | |
| status: | Triaged → In Progress |
Revision history for this message
| Michael Nelson (michael.nelson) wrote | #2 |
| Changed in soyuz: | |
| status: | In Progress → Fix Committed |
| Changed in soyuz: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The portlet should not link the binary names and add some text saying they're awaiting acceptance. Easily done via checking the PackageUpload status.