--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: debian-cd: please mention the dinstall serial in a trace file
- From: Cyril Brulebois <kibi@debian.org>
- Date: Fri, 11 Nov 2016 03:31:09 +0100
- Message-id: <20161111023109.4043.12723.reportbug@armor.home>
Package: debian-cd
Severity: normal
(X-D-Cc: debian-boot@lists.debian.org)
Hi,
Since pettersson has a mirror with project/trace, which gives us access
to archive serial, it would be nice to have a look when the build starts
and to report this, maybe in a trace file alongside cdimage.debian.org?
Also, as as side question, do we prevent the mirror from being updated
during the n-hours build of all images?
Some context: This would help figure out what changed between two d-i
releases, in addition to log parsing scripts I'm already running (which
only accounts for udebs installed during the build, plus build-deps):
looking at packages getting ACCEPTED between two dates in my
debian-boot@ mailbox is not practical and is missing non-debian-boot@
packages; plus: those udebs might not have reached testing anyway.
Thanks for considering.
KiBi.
--- End Message ---
--- Begin Message ---
Pushed to the setup git repo, so marking this fixed. Thanks for the patch!
On Tue, Apr 25, 2017 at 01:03:22AM +0100, Steve McIntyre wrote:
>On Thu, Apr 13, 2017 at 02:43:24PM +0200, Cyril Brulebois wrote:
>>Cyril Brulebois <kibi@debian.org> (2016-11-11):
>>> Since pettersson has a mirror with project/trace, which gives us access
>>> to archive serial, it would be nice to have a look when the build starts
>>> and to report this, maybe in a trace file alongside cdimage.debian.org?
>>
>>Here's a prospective and untested patch.
>>
>>ISTR we (ab)use cronjob.weekly for release builds, but feel free to
>>test/adjust before pushing to the repository.
>
>Looks good (ish!) The code's fine, but I'll move it to the setup.git
>repo. The code in debian-cd/contrib is just a convenience copy for
>publishing what we do in the package.
>
>>> Also, as as side question, do we prevent the mirror from being updated
>>> during the n-hours build of all images?
>>
>>Answer welcome. :)
>
>Nope. For any given architecture build, we do ~all the parsing
>up-front so it's going to be consistent. But from one arch to the next
>it's possible that things will update.
>
>
>--
>Steve McIntyre, Cambridge, UK. steve@einval.com
>< sladen> I actually stayed in a hotel and arrived to find a post-it
> note stuck to the mini-bar saying "Paul: This fridge and
> fittings are the correct way around and do not need altering"
--
Steve McIntyre, Cambridge, UK. steve@einval.com
"The problem with defending the purity of the English language is that
English is about as pure as a cribhouse whore. We don't just borrow words; on
occasion, English has pursued other languages down alleyways to beat them
unconscious and rifle their pockets for new vocabulary." -- James D. Nicoll
--- End Message ---