Hi,
On Freitag, 6. Februar 2015, Niels Thykier wrote:
> > debian-installer-netboot-images (20150107) unstable; urgency=low
> > * Bump debhelper compat level to 9.
so I went ahead and prepared the uploaded in git, reverted this change and
added myself to uploaders even and then upon running "dch -r" I noticed the
version, which was set to 20150108, which is neither todays date nor, more
importantly, the date of the d-i release it contains. Bummer.
The README says:
* Note about versioning:
- This package's version is simply the version of the d-i netboot
images it fetches and ships.
- Since d-i can be binNMU'd in stable (usually to get built against
a newer kernel in proposed-updates, when no source changes are
planned for stable), its version ends with +bN; using the exact
same version for this package wouldn't work too well because a
couple of assumptions are made in the Debian infrastructure
(notably in dak) when a binNMU-like version number is seen. To
work around those, the .bN suffix is used instead of the usual
+bN suffix.
but I don't think using a binNMU version for a normal upload would be smart.
Given this, and given that the debhelper compat bump was announced in May 2013
and committed in June 2013, I wonder whether the cleanest cause of action
wouldnt just be to accept this debhelper bump?!?
(Another option would be to delay the upload until the next d-i release, but
IMO that would be even worse, as debian-lan-config, debian-edu and debian-edu-
config all rely on this package and thus cannot be tested properly since
basically forever.)
cheers,
Holger
Attachment:
signature.asc
Description: This is a digitally signed message part.