Linking a package to upstream is confusing
Bug #315239 reported by
Curtis Hovey
This bug report is a duplicate of:
Bug #83357: "Link to Ubuntu Package" doesn't allow choosing a release.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
I was looking to associate the packaged versions of 'eject' with the upstream series (there's only the 'main' series at this point).
Going from the 'eject' side of things, this page only let me specify the association for the latest release--that is, Jaunty.
https:/
Going from the 'eject (Ubuntu)' side of things, this page lets me specify the association for all currently-supported releases.
https:/
I found this to be somewhat confusing. Is there a good reason for things to be like this--a task is sort-of doable from one interface, and completely doable from another--or should I convert this question to a bug against Malone?
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
| Changed in launchpad: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| tags: | added: package-link |
To post a comment you must log in.
I agree this is a bug. While the user can complete his task, he may have to fail a few times. This is bad. This can be addressed in the package linking effort that the Launchpad Registry Team will undertake in 2009