Bug#725321: [UDD]: Please make a "BTS might be confused" script/query
On 04/10/13 at 15:23 +0200, Niels Thykier wrote:
> On 2013-10-04 08:43, Niels Thykier wrote:
> > Package: qa.debian.org
> > Severity: wishlist
> >
> > Hi,
> >
> > There are a number of cases where the Debian Bug Tracker can become
> > "confused" or (to many) behave surprisingly. The most common example
> > is when a bug in marked as "found" and "fixed" in the same version.
> >
> > In this case, the BTS silent accepts the values but ignores the
> > "fixed" version and counts the bug as "unfixed" in that version.
> > Accordingly, the bug will still count until either the "found" version
> > or the "fixed" version is removed[1].
> >
> > I think it would be nice if we had some easy way to get a list of all
> > bugs where the BTS is (possibly) "confused", so we can easily resolve
> > those problems.
> >
> > As mentioned, one type of problem like this is when a bug has a fixed
> > version equal to a found version. A second type of issue is the use
> > of "binNMU" versions in fixed or found versions; I am pretty sure the
> > BTS does not know of binNMUs, but I have seen people use it in the
> > past.
> >
> > Thank you in advance,
> > ~Niels
> >
> > [1] It is possible that the BTS behaves sensible if you mark a later
> > version "fixed" as well. Haven't tried.
> >
>
> I think the first type of "confusion" can be detected via the query:
>
> SELECT * FROM public.bugs_fixed_in fixed, public.bugs_found_in found
> WHERE fixed.id=found.id AND fixed.version = found.version;
Hi,
I've implemented this in
http://udd.debian.org/cgi-bin/bts-is-confused.cgi
but not yet Ivo's suggestion.
Lucas
Reply to: