Re: Bug#789181: apt-listbugs: should not list fixed bugs

Francesco Poli <[email protected]> Sat, 20 Jun 2015 10:35:48 +0200
Newsgroups	gmane.linux.debian.devel.debbugs
Message-ID	<[email protected]>
Control: tags -1 - moreinfo
Control: reassign -1 debbugs 2.4.1.1

On Fri, 19 Jun 2015 21:28:01 +0200 Vincent Lefevre wrote:

> On 2015-06-19 19:06:10 +0200, Francesco Poli wrote:
> > I propose that this bug report is reassigned to debbugs, requesting a
> > modification of the BTS to automatically join found and fixed version
> > lists, when merging bugs and to keep those lists in sync among merged
> > bugs.
> > Of course, the documentation should be changed accordingly.
> > 
> > I'll reassign this bug report myself, if you don't object.
> > 
> > Please let me know what you think.
> 
> I completely agree.

Here we go!


Dear debbugs maintainers, Vincent Lefevre reported a bug against
apt-listbugs (which I maintain). During the conversation that followed,
it was found out that the Debian BTS does not guarantee that merged bug
reports share the same version tracking info.

In other words, it is possible that two merged bugs have different
"found" and "fixed" version lists.
One example is bug #787364, which is merged with bug #787263.
The former [1] is

  Merged with 787263
  Found in versions systemd/220-1, systemd/220-2, systemd/215-18,
systemd/220-4, systemd/220-5, systemd/219-10
  Fixed in version systemd/220-3

while the latter [2] is

  Merged with 787364
  Found in versions systemd/220-2, systemd/220-1
  Fixed in version systemd/220-3

[1] https://bugs.debian.org/787364
[2] https://bugs.debian.org/787263

The result is that the BTS claims that one bug is fixed in current
unstable (systemd/220-7), while the other bug is still present.
Does this make sense?
I mean, the two reports are merged with each other, hence they are
considered as two duplicate reports for the same issue.
This issue is either present or absent in a given version of the
package under consideration: how come the BTS claims that this issue
is present and absent at the same time in the same version?

Unless I misunderstand something, this should not happen.

If you agree that this is an inconsistency, I think that debbugs should
guarantee that merged bug reports share the same "found" and "fixed"
version lists.
This could be done by automatically joining the "found" version lists
of the bug reports being merged (just like what is done with tags).
Then, any alteration performed to the "found" version list of one bug
report should be automatically propagated to the other merged bug
reports. The same should hold for "fixed" version lists.

Obviously, the documentation [3] should be updated accordingly.

[3] such as: https://www.debian.org/Bugs/server-control#merge


Please fix this bug.

Thanks for your time!
Bye.

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
..................................................... Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE
signature.asc (application/pgp-signature, 819 B)