Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: tpu
Hi dear Release Team,
I just got reminded that win32-loader embeds various other packages and
that it would be great to have its subparts updated for the Wheezy
release; namely, from it's current Built-Using field:
cpio (= 2.11-8)
=> 2.11+dfsg-0.1, same in unstable/testing
debian-archive-keyring (= 2012.4)
=> No change
gnupg (= 1.4.12-4)
=> 1.4.12-7, same in unstable/testing
grub2 (= 1.99-22.1)
=> 1.99-27+deb7u1 in testing, 1.99-27.1 in unstable
gzip (= 1.5-1.1)
=> No change
ipxe (= 1.0.0+git-20120202.f6840ba-3)
=> No change
loadlin (= 1.6e-2)
=> 1.6f-1
So grub2 being different in testing is the reason why win32-loader's
no-change rebuild would have to go through t-p-u. Of course I can upload
a no-change rebuild to unstable first to fulfill the version
constraints.
win32-loader needs an FTP-master action for the debian/tools/* change;
and it will need to also be handled on release day.
What do you think ?
Cheers,
OdyX
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (500,
'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
