Bug#843943: debian-cd: please mention the dinstall serial in a trace file

2017-04-24 Thread Cyril Brulebois
Steve McIntyre  (2017-04-25):
> 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.

Alright, thanks!

> >> 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.

It looks good enough, yeah; at least it seems to have worked just fine
so far. :-)

Thanks again.


KiBi.


signature.asc
Description: Digital signature


Bug#843943: debian-cd: please mention the dinstall serial in a trace file

2017-04-24 Thread Steve McIntyre
On Thu, Apr 13, 2017 at 02:43:24PM +0200, Cyril Brulebois wrote:
>Cyril Brulebois  (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.st...@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"



Bug#843943: debian-cd: please mention the dinstall serial in a trace file

2017-04-23 Thread Cyril Brulebois
Hi,

Cyril Brulebois  (2017-04-13):
> Cyril Brulebois  (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.
> 
> > Also, as as side question, do we prevent the mirror from being updated
> > during the n-hours build of all images?
> 
> Answer welcome. :)

Friendly ping. The sooner we get this merged, the sooner I can get easier,
quicker, and possibly more complete tools for release management.

Thanks already.


KiBi.


signature.asc
Description: Digital signature


Bug#843943: debian-cd: please mention the dinstall serial in a trace file

2017-04-13 Thread Cyril Brulebois
Cyril Brulebois  (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.

> Also, as as side question, do we prevent the mirror from being updated
> during the n-hours build of all images?

Answer welcome. :)


KiBi.
From 07ad313e6d7ff5948c0ceed8b066687a580751b9 Mon Sep 17 00:00:00 2001
From: Cyril Brulebois 
Date: Thu, 13 Apr 2017 14:40:50 +0200
Subject: [PATCH] Store archive serial in trace directory.

Mostly useful for the Debian Installer release manager.

Closes: #843943
---
 contrib/common.sh  | 9 +
 contrib/cronjob.weekly | 5 +
 2 files changed, 14 insertions(+)

diff --git a/contrib/common.sh b/contrib/common.sh
index 9190a37..3ce712e 100644
--- a/contrib/common.sh
+++ b/contrib/common.sh
@@ -147,3 +147,12 @@ arch_has_firmware () {
 done
 return 1
 }
+
+get_archive_serial () {
+trace_file="$MIRROR/project/trace/ftp-master.debian.org"
+if [ -f "$trace_file" ]; then
+awk '/^Archive serial: / {print $3}' "$trace_file"
+else
+echo 'unknown'
+fi
+}
diff --git a/contrib/cronjob.weekly b/contrib/cronjob.weekly
index 5019508..f16e19e 100755
--- a/contrib/cronjob.weekly
+++ b/contrib/cronjob.weekly
@@ -64,6 +64,11 @@ if lockfile -r0 $BUILDLOCK ; then
 echo "git update debian-cd"
 cd debian-cd && git pull ; cd ..
 
+# Keep track of the serial for the archive we're building against,
+# for later archive diffing for release announce preparation:
+serial=$(get_archive_serial)
+echo "$serial" > $PUBDIRJIG/trace/archive-serial
+
 # Work out the default desktop, and do *not* build a CD1 for that
 # desktop - it'll be done in the full set anyway
 TASKSEL_DEB=$(./debian-cd/tools/which_deb ${MIRROR} testing task-desktop binary)
-- 
2.1.4



signature.asc
Description: Digital signature


Bug#843943: debian-cd: please mention the dinstall serial in a trace file

2016-11-10 Thread Cyril Brulebois
Package: debian-cd
Severity: normal

(X-D-Cc: debian-b...@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.