Linkify Debian bug numbers in comments correctly

[Michael Bienia]

When mentioning a Debian bug number in a bug comment it gets linkified to a LP bug with the same number (which doesn't exist (yet)).

I usually use "Debian bug #321456" in a comment when I want to point to a Debian bug which is related to this bug report. This gets transformed to a link which points nowhere useful.

If possible recognize that this is a Debian bug number and add a correct link or don't linkify it at all (if the bug number doesn't exist in malone)

[Matthew Paul Thomas (mpt)]

Michael's parenthetical aside is bug 4595, but the main problem -- linking Debian bug reports correctly -- is not a duplicate.

[James Henstridge (jamesh)]

Perhaps a better system would be this:

1. Change the search regex from "bug ..." to "($LPNAME )?bug ..." where LPNAME is a regex matching a valid Launchpad name
2. Look up $LPNAME in our list of external bug trackers.
3. If it is found, generate the appropriate bug tracker link, and link the entire text.
4. If not, just like the "bug ..." bit to the corresponding Launchpad bug report.

The Idea being to handle this for more than just the Debian bug tracker.

[era (era)]

This is rampant in comments imported from bug watches. Is there a separate bug report for Mozilla bugs, or should that just be added here?

For example, LP bug #15224 comment 17 [1] should obviously be linked to https://bugzilla.mozilla.org/show_bug.cgi?id=96579 and not to https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/96579

([1] That's https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/96579 in case that isn't linkified correctly either :-)

[William Grant (wgrant)]

On 21/02/13 23:41, era wrote:
> This is rampant in comments imported from bug watches. Is there a
> separate bug report for Mozilla bugs, or should that just be added here?

That's bug #505760.