Poor handling of a distribution being its own upstream for a package

Reported by Matthew Paul Thomas on 2006-12-19
64
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned

Bug Description

In some cases, a particular distribution is the upstream for some software. Examples include Notify OSD, Ubiquity, Upstart, the Ubuntu Documentation, and Ubuntu Software Center, all of which are designed for Ubuntu first and foremost.

In these cases, the benefit of keeping generic bugs and distribution-specific bugs separate is less than the cost of having two possible places to report bugs about exactly the same software. But even when this is obvious, which of the two is the best place is not. For example:

* Bug 200910 describes how Ubuntu uploads to the ubuntu-docs package should, but don't, automatically mark ubuntu-docs project bug reports as fixed.
* The Notify OSD maintainer prefers bugs to be reported on the upstream project (as shown for example in bug 415015).
* The previous Ubuntu Software Center maintainer preferred bugs to be reported on the Ubuntu package. The current maintainer prefers bugs to be reported on the project.
* The Upstart maintainer prefers bugs to be reported on the upstream project (which contributed to confusion in bug 557177).
* The Ubuntu SSO client maintainer prefers bugs to be reported on the upstream project.
* The Unify project <https://launchpad.net/unify> exists partly as a workaround for this bug as it affects Unity.
* In November 2013, Ubuntu Touch standardized on reporting bugs on the package rather than the project. <https://lists.ubuntu.com/archives/ubuntu-devel/2013-November/037821.html>

There should be some way to handle this specially. Colin Watson said "I'd love to have bugs (optionally) transparently gatewayed from one to the other".

Bug 3152 and bug 138545 are suggestions for the converse case, where an upstream project wants to see bugs reported about packages of the project as well.

The Translations equivalent is bug 28524, so it would save time to design the fix for that bug at the same time.

description: updated
Björn Tillenius (bjornt) wrote :

I don't know how we can fix this bug, but we should fix it somehow.

Changed in malone:
importance: Undecided → Medium
status: New → Triaged
description: updated
description: updated
description: updated
description: updated
summary: - Handle a distribution being its own upstream for a package
+ Poor handling of a distribution being its own upstream for a package
description: updated
Curtis Hovey (sinzui) wrote :

I recently added a link in the search form that lets the user switch between the project and package listings. There are two things we can do to improve this.

1. Preserve the search criteria in links and ordering so that when my search fails, I can use the upstream-downstring to perform the search. This is somewhat was to do and will fix 3 other bugs. This addresses my disappointment when adding the links.

2. But what I really want is a search option
   [x] Include reports in <fnord-project|Ubuntu package: libfnord, fnord-ui>
that shows a union of bugs.

description: updated
description: updated
Changed in launchpad:
importance: Medium → Low
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers