[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#698430: marked as done (UDD: rcbugs.cgi shows #639407 as affecting Wheezy, but it is fixed+archived)



Your message dated Tue, 29 Jan 2013 16:48:32 +0100
with message-id <20130129154832.GB6501@xanadu.blop.info>
and subject line Re: Bug#698430: UDD: rcbugs.cgi shows #639407 as affecting Wheezy, but it is fixed+archived
has caused the Debian Bug report #698430,
regarding UDD: rcbugs.cgi shows #639407 as affecting Wheezy, but it is fixed+archived
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
698430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698430
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: qa.debian.org
Severity: normal
User: qa.debian.org@packages.debian.org
Usertags: udd

Using a filtered query of RC bugs affecting Wheezy (but not sid and
without an unblock hint)[1], I noticed #639407  being listed.  However,
according to the BTS #639407 is closed, fixed in 2.7.3-1 (Wheezy has
2.7.3-6) _and_ it is archived[2].

I am not sure how and why, but it appears to be the database itself
that is outdated/<insert more accurate word(s) here>.  This bug is
also present in quantz.d.o's UDD instance (no pun intended).

 $ /usr/bin/psql -h localhost -p 5441 -U guest  udd
 udd=> SELECT id,source FROM public.bugs_rt_affects_testing WHERE id = 639407;
    id   |  source
 --------+-----------
  639407 | python2.7
 (1 row)


~Niels

[1] http://udd.debian.org/bugs.cgi?release=wheezy_not_sid&merged=ign&unblock-hint=ign&fnewerval=7&rc=1&sortby=id&sorto=asc&chints=1&ctags=1&cdeferred=1&crttags=1

[2] The latter suggesting that the bug has been fixed in testing for
over a month now.

--- End Message ---
--- Begin Message ---
On 19/01/13 at 19:30 +0000, Steven Chamberlain wrote:
> Hi,
> 
> Based on a diff of RC bug numbers according to UDD bugs.cgi vs. britney
> testing-nr [0] the surplus bugs are:
> 
> #639407 python2.7-dev [not marked as 'found' in any version; archived]
> #672677 src:broadcom-sta [marked fixed in wheezy+sid; archived]
> #677822 nut-server [marked fixed in wheezy+sid; archived]
> #682000 nut-client [marked fixed in wheezy+sid; archived]
> #684392 nut-server [marked fixed in wheezy+sid; archived]

Hi,

None of those bugs are listed as affecting wheezy currently.

> #677054 nut-client [marked fixed in wheezy+sid; archived]

This one is, but rightfully.

I suspect that testing-nr does not look at archived bugs. It's possible
that archived bugs start affecting wheezy again, e.g. when someone
messes up the package changelog and branches from an affected version.

I've re-done a diff between testing-nr and UDD, and did not find
anything wrong. So I'm closing the bug, but feel free to reopen if you
run into strange things again.

Lucas

--- End Message ---

Reply to: