Managing bugs with a ubuntu-specific package

Asked by Dean Sas

Hi,

Currently the ubuntu-docs team has two places to manage bugs, the ubuntu-docs package and the ubuntu-doc project. All of the bugs on one are also bugs on the other (with the exception of 3-4 "workflow" bugs each year) as we manage our own debian packaging in the project bzr repository.

To make both places list all bugs we have to change the status/importance twice. If we don't do that then we have to check both places when we're managing bugs.

Is there something we can do to make managing bugs easier?

Thanks,
Dean

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
Björn Tillenius Edit question
Last query:
Last reply:
Whiteboard:
Bjorn, can you please clarify what could be done in this scenario ? ubuntu-docs is a ubuntu native source code, i.e. there is not distinction between upstream and package. Shall they disable bugs upstream and leave only with sourcepackage bugs ?
Revision history for this message
Matthew East (mdke) said :
#1
Revision history for this message
Matthew East (mdke) said :
#2

The other problem that this causes is that when uploading a package to Ubuntu with a fix for this bug, inserting the LP bug number in the Ubuntu package changelog does not automatically mark the bug report as "fix released" if the bug report is on the "ubuntu-doc" project, rather than the "ubuntu-docs" Ubuntu package.

Revision history for this message
Dean Sas (dsas) said :
#3

This question wasn't supposed to be marked as resolved.

Revision history for this message
Björn Tillenius (bjornt) said :
#4

Unfortunately, there is no good solution to this problem today. The best I can suggest is to mark the ubuntu-doc project as not tracking bugs in Launchpad. You could then add some text to ubuntu-doc's description, saying that all bugs are tracked in https://launchpad.net/ubuntu/+source/ubuntu-docs.

Can you help with this problem?

Provide an answer of your own, or ask Dean Sas for more information if necessary.

To post a message you must log in.