On Wed, Sep 12, 2007 at 04:40:58PM -0700, Don Armstrong wrote: > On Wed, 12 Sep 2007, Jens Seidel wrote:
> If you're looking at > http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=hex-a-hop;dist=unstable, > what you are seeing is the fixed/found/absent status of bugs in the > source package in unstable. OK, this is what I initially expected. > This means that since you just uploaded -5, it only recently was added > to the archive. So for a brief period of time[1] bugs that had been > fixed in -5 would be "done" but not fixed. The opposite is true: Immediately after an upload the bug status looks good. A few days later (e.g. today) it is wrong again!? > > No, I looked only at the source status. So I probably misinterpreted > > the "built on all architectures" statement. > > If you're looking at src= page, it only cares about the version of the > source package. Have a look at http://bugs.debian.org/cgi-bin/pkgreport.cgi?ordering=normal;archive=0;dist=unstable;repeatmerged=1;src=hex-a-hop It lists e.g. #439393 as "Outstanding bug". To be honest this may be a corner case as the bug was filed against a prelease of version -4 but used "Version: -4". It was closed in the official -4 upload! Not a corner case is #438857. Bug was opened against -3 and closed in -5 and is still outstanding. (The archive pulse should happened already, right?) There are many further bugs wrongly displayed! PS: Please CC: me! Shouldn't you do this on default for bug reports as users are normally not subscribed and I didn't set any special header? Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
