#753683 Bugs in binary packages which have migrated from one source package to another show up in the wrong source package

#753683#5
Date:
2014-07-04 10:32:38 UTC
From:
To:
Dear maintainer,

thanks for the new package tracker. ;)

Looking at [1] I find it strange, that it says:
'1 bug tagged help in the BTS'
While at the same time there is no open bug and indeed clicking on the
'1 bug' link leads to [2] without a bug.

Probably the tracker finds #591881 and doesn't realize that this is
already closed.

Best regards,
Andreas


1: https://tracker.debian.org/pkg/ffmpeg
2:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ffmpeg&tag=help&pend-exc=done

#753683#10
Date:
2014-07-08 21:41:51 UTC
From:
To:
[ Cc owner@bugs.debian.org for a question ]

No, in fact, the tracker finds #704070. The status information about
this bug as returned by the BTS is the following:

$ bts status 704070
bug_num	704070
log_modified	1390397228
id	704070
found	libav/6:0.8.5-1 =>
pending	pending
date	1364400182
package	ffmpeg
location	db-h
msgid	<CADdDZR=J=1N6oV8HmZgOJ4a3+xG5SmoJBeBwtCPpwyP6t3+KTQ@mail.gmail.com>
keywords	help wontfix
severity	minor
source	ffmpeg, ffmpeg-debian, ffmpeg-free, libav
last_modified	1390397228
tags	help wontfix
found_versions	libav/6:0.8.5-1
subject	ffmpeg: obsolete-conffile as reported by adequate
originator	shirish शिरीष <shirishag75@gmail.com>

Right now we rely on the "package" field to assign the bugs tagged
help to the corresponding source package.

The old PTS uses the same information but does a supplementary binary->source
mapping on top of this field.

It would be nice if we could just use the "source" field instead of doing
our own mapping bug the value of the "source" field doesn't make much sense
to me... why does it list so many source packages and not only
one like on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704070 ?

Cheers,

#753683#15
Date:
2014-12-01 09:23:17 UTC
From:
To:
Thanks for reporting,
Christophe

#753683#20
Date:
2014-12-01 09:53:26 UTC
From:
To:
Control: reopen -1
Control: retitle -1 Bug->package assignment does not work correctly

Why are you closing this bug?

I explained in my first answer that the behaviour of the tracker is not
correct. I never got the expected answer from the bugs.d.o maintainer
but there's a real problem to fix (even though the specific issue reported
might be gone, I haven't checked).

Cheers,

#753683#29
Date:
2014-12-01 17:53:53 UTC
From:
To:
Sorry; I missed this the first time around until Paul Wise pinged me on
IRC about it.

You should just use the source field. It is very difficult to get the
package->source mapping right without all of the information that the
BTS has at its disposal.

It lists multiple sources because this bug was filed against the ffmpeg
binary package, which is built from those sources, but then had a found
version which matched libav. The BTS errs on the side of including all
relevant source packages in cases like this.

#753683#34
Date:
2014-12-02 08:35:36 UTC
From:
To:
Well, the BTS is inconsistent then. Because it lists all sources packages
here but the bug did not show up in the list of bugs affected against the
"ffmpeg" source package, which is what got reported to us in the first
place.

And as I said, the individual bug page also doesn't show up all sources
packages. So should I use "source" as a base and then restrict to the set
of source packages available in "found_versions" (if any)?

Cheers,

#753683#39
Date:
2014-12-03 10:51:44 UTC
From:
To:
[ Reordering the paragraph ]

So let me explain, we use the BTS soap interface to retrieve a list of
bugs tagged "help" which are not closed yet. Then we assign those bugs
to source packages and display a message "heh you have X bugs tagged
help" and give a link of the form
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ffmpeg&tag=help&pend-exc=done

In this report, the above linked showed nothing while the status of the
bug 704070 was this (dropping irrelevant fiels):

found	libav/6:0.8.5-1 =>
pending	pending
package	ffmpeg
keywords	help wontfix
severity	minor
source	ffmpeg, ffmpeg-debian, ffmpeg-free, libav
tags	help wontfix
found_versions	libav/6:0.8.5-1

(This can no longer be reproduced with this specific bug since it got
reassigned in the mean time)

Apparently that was not the case (cf above).

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704070

(again now it's irrelevant since the only associated source is now libav
due to the reassign)

Cheers,

#753683#44
Date:
2014-12-04 01:31:48 UTC
From:
To:
Control: reassign -1 debbugs
Control: affects -1 tracker.debian.org
Control: retitle -1 Bugs in binary packages which have migrated from one source package to another show up in the wrong source package

OK. I now understand what is going on here.

In wheezy, libav is the source package for the ffmpeg binary package.

In sid, ffmpeg is the source package for the ffmpeg binary package.

Unfortunately, the BTS (currently) only considers the state of
source/binary packages in sid when it's displaying bugs using the
pkgreport.cgi?src=foo search. Thus, if ffmpeg wasn't in the ffmpeg
source package in sid at that moment in time, this wouldn't have worked.

This is basically a bug in the BTS itself, but it's complicated to fix.

Fixing it requires me knowing all of the binary packages which were
ever in a particular source package, and also tracking all of the source
package renames which happen. It's tied up with doing the database for
the BTS properly too.

Anyway, if you're using the src= search (which you are, since
tracker.debian.org is by source package), then you should show the bug
in all of the source packages which are in the source field. Eventually
the BTS will show them all correctly using the links that you're already
using.