Link bugs in ubuntu packages to the actual project

[Dennis Schridde]

https://bugs.launchpad.net/ubuntu/+source/warzone2100 shows bugs for warzone2100, but https://bugs.launchpad.net/warzone2100 does not. This is even though both are linked.

[Matthew Paul Thomas (mpt)]

Dennis, what do you mean by "both are linked"?

Currently none of the bugs listed at <https://bugs.launchpad.net/ubuntu/+source/warzone2100> are recorded as also affecting upstream Warzone 2100. That's why they don't show up at <https://bugs.launchpad.net/warzone2100>.

[Christian Reis (kiko)]

On Thu, Mar 20, 2008 at 12:35:44AM -0000, Matthew Thomas wrote:
> Dennis, what do you mean by "both are linked"?

He means the packaging information that is displayed at the bottom right
of:

    https://edge.launchpad.net/warzone2100/

I think we should file a new bug to cover this as we need to either
forbid adding these records and sanitize information, or rethink the
deletion UI.
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125

[Matthew Paul Thomas (mpt)]

Ok, I've reported bug 204117 about that problem, but it doesn't seem related to this bug report.

[Dennis Schridde (devurandom)]

So to make a bugreport to the Ubuntu package of warzone2100 also show up in the warzone2100 launchpad-bugs-section, I would have to select "Also affects project" on that bug? That will not happen automatically?

[Christian Reis (kiko)]

Yes. The short explanation is that a bug in the packaged version may be
caused by the act of packaging, and not the original source code. Does
that make sense?

[Dennis Schridde (devurandom)]

It does.

[Matthew Paul Thomas (mpt)]

In future we'll make it more obvious that the next step, for a bug report filed on a package but not on a project, is to check and record whether the bug occurs in the upstream project.

[Sam Brightman (sambrightman)]

Honestly, I don't think it's enough to provide it as a next step. A lot of people seem to agree that the current arrangement is plain confusing. It's not just submitters that will have this issue - in fact, I think un-logged-in people searching for bugs is probably the most common case.

[Matthew Paul Thomas (mpt)]

Fixing bug 3152 should reduce that confusion a lot. I appreciate that it is awkward for Launchpad to have separate bug listings for projects and packages. But this is integral to why Launchpad exists: to improve collaboration between distributors and upstream developers, while minimizing noise from issues that are specific to one or the other. See also bug 76416.