When someone subscribe a bug and a mailing list both, and the mailing list
subscribe this bug, then the bellow will happen

Some one send an post to mailing list and bug both

Re: Bug#1234567: something wrong happens

The mailing list will give subscriber

Re: Bug#1234567: something wrong happens

While BTS gives subscriber

Bug#1234567: Re: Bug#1234567: something wrong happens

Then this will happen always and the subject will be longer and longer.
It will also break the thread.

Please consider don't add something like Bug#1234567: when the subject
has one for now.

Control: tag -1 moreinfo unreproducible
References: or In-Reply-To: headers.[1] The BTS tries very hard to
never break threading by stripping References, Message-Id, or
In-Reply-To; cases where it does are bugs.

The BTS doesn't actually add Bug#12345 if the existing bug report
already has the correct Bug number. [If the report has the wrong bug
number, it will add the correct one to the front.]

You can see examples of this working correctly here:

http://lists.debian.org/debian-ctte/2012/11/ for example

Don Armstrong

1: A possible exception to this would be if your MUA was broken or
substandard, but that's an MUA problem.

See this please.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687396

Maybe BTS is confused by mailing list tag like [buildd-tools-devel]

Ah, ok. In general, the BTS should figure out mailing list tags if the
list headers are still intact. If not, it assumes that you knew what
you were doing, and leaves them alone. [It's sort of dangerous to
assume that anything in brackets is a mailing list tag, which is why
Debbugs doesn't strip them; it's also kind of annoying for mailing
lists to add them, as this information is trivially available in the
message headers, but then again, not everyone sees those message
headers.]


Don Armstrong

I don't ask to strip mailing list tag, I means that we shouldn't add #687396
twice.

Detect whether subject has #687396 (The same as current bug number, not
bug#.*), if it already has one, don't add it twice.

I'd like to second the notion that this is a real bug, and that it
should be addressed - e.g.

http://lists.alioth.debian.org/pipermail/piuparts-devel/2014-March/thread.html#5197

I agree with #27 that the solution could be to check for the presence
of a "Bug#" in the subject before adding one.

I suggest that the 'unreproducible' and 'moreinfo' tags be removed
from this bug.

Mailman mailing lists consistently add [] headers, which causes debbugs
to include additional Bug#, which then get added to. Detect this, and
only add bug# to Subject: if they don't exist anywhere in the subject.

See
http://lists.alioth.debian.org/pipermail/piuparts-devel/2014-March/thread.html#5197
for an example.

The git source code repository is referenced from the wiki page [1].

The problem appears to be in the Perl 'process' script. There are a number
of places where the bug number and $newsubject are concatenated to make a
new subject, without checking to see if the bug number is already there.
Replace those occurrences with a function that does the check first? ... or
strip the bug number from $newsubject.

1 - https://wiki.debian.org/BTS

Dear Customer,

Your item has arrived at the USPS Post Office at January 22, but the courier was unable to deliver parcel to you.

Please check delivery label attached!

Best regards,
Franklin Bright,
USPS Senior Station Manager.

Dear Maintainers

Here my patch proposal for this bug.

Cheers,

Today is the sixth anniversary of this bug. The submitted patch is one year
old.

This bug is almost ten years old; a patch was added almost five years
ago.

Does anyone have time to review the patch that was submitted back in 2017?

2017 patch:
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=695188;filename=0001-Fix-695188-intelligent-add-of-Bug-XXXXXX.patch;msg=60