Re: Bug#570346: nmu: gnucash_2.2.9-4
[This was answered on IRC, but for completeness...]
On Fri, 2010-02-19 at 13:58 +0100, Joachim Breitner wrote:
> Am Freitag, den 19.02.2010, 11:42 +0000 schrieb Adam D. Barratt:
> > > ok, then maybe something is broken with
> > > https://buildd.debian.org/status/package.php?p=gnucash
> > > because only 2.2.9-4 is listed for amd64?
> >
> > It's a feature.
> >
> > Both /status/package.php and /pkg.cgi only display binNMUs until they're
> > uploaded, and then revert to the source version. This is a side-effect
> > of the fact that wanna-build only stores the binNMU information during
> > the time between the binNMU being scheduled and it being uploaded; the
> > wanna-build commands used to build the pages therefore only output
> > references to the binNMU version during that time.
> >
> > https://buildd.debian.org/build.cgi?pkg=gnucash shows logs for all
> > versions of the package, including binNMUs.
>
> hmm, thanks for the information. This is a recent change, isn’t it?
It's certainly been the behaviour for as long as I can remember.
> Is the information reverted when package is uploaded, or when it’s
> installed? I.e. is there a time frame where I would not know about a
> binNMUed package from either the archive or the wanna-build dump?
The binNMU information is removed when the package is installed. To be
precise, when wanna-build processes a Packages file which contains
either the binNMU or a newer version.
(It's also removed when the package is marked not-for-us and in a few
other circumstances but none of those affect the Uploaded / Installed
boundary afaics).
> /me finds this all very confusing, especially WRT to handling binNMU
> campaigns.
>
> I was about to check whether
> https://buildd.debian.org/stats/amd64-dump.txt.gz
> also lacks the binNMU data, but it seems like that file has not been
> updated since somewhen in January. Will that file be available
> eventually?
This is now #570512.
Regards,
Adam
Reply to: