Source package shows historic upstream
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Curtis Hovey |
Bug Description
The source package page uses the historic packaging object when there is no packaging link for the current series. This makes it impossible to create the packaging link for the current series (you can only edit the historic one). This also causes misunderstandings where https:/
Old erroneous description of the root cause:
https:/
Related branches
- Jeroen T. Vermeulen (community): Approve (code)
-
Diff: 215 lines (+47/-89)2 files modifiedlib/lp/registry/doc/sourcepackage.txt (+38/-61)
lib/lp/registry/model/sourcepackage.py (+9/-28)
summary: |
- +needs-packaging includes packages that has upstream links + Source package shows historic upstream |
description: | updated |
tags: | added: package-link |
tags: | added: qa-ok |
Changed in launchpad-registry: | |
status: | In Progress → Fix Committed |
The report is correct. The SP UI is lying. The page is using the packaging link from karmic because lucid does not have one. It is not clear from the UI that a guess is being made.
This behaviour is historic. The initialize- from-parent script did not copy packaging links forward, so the UI would guess at the correct packaging link. This proved to be problematice because without a proper representation of the state in the schema, it was difficult to know the true state of packaging, and Launchpad often (such as in this very case) contradicts itself.
The correct behaviour is to remove the guess logic. Instead, the UI can ensure that the previous upstream project is in the list of projects that the sp page will propose. The page should also make it easy to see what the previous upstream project was. Users will rarely need to set this because the initialize- from-parent does copy the packaging links from the parent series to the current series.