Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * FAILED BUILD: amd64 Feb 28 00:04 buildd@barber build_cdrom_isolinux http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_isolinux.log * FAILED BUILD: amd64 Feb 28 00:05 buildd@barber build_cdrom_gtk http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_gtk.log * FAILED BUILD: amd64 Feb 28 00:06 buildd@barber build_cdrom-xen http://d-i.debian.org/daily-images/amd64/daily/build_cdrom-xen.log * FAILED BUILD: amd64 Feb 28 00:07 buildd@barber build_netboot http://d-i.debian.org/daily-images/amd64/daily/build_netboot.log * FAILED BUILD: amd64 Feb 28 00:08 buildd@barber build_netboot-gtk http://d-i.debian.org/daily-images/amd64/daily/build_netboot-gtk.log * FAILED BUILD: amd64 Feb 28 00:09 buildd@barber build_netboot-xen http://d-i.debian.org/daily-images/amd64/daily/build_netboot-xen.log * FAILED BUILD: amd64 Feb 28 00:10 buildd@barber build_hd-media http://d-i.debian.org/daily-images/amd64/daily/build_hd-media.log * FAILED BUILD: amd64 Feb 28 00:10 buildd@barber build_hd-media_gtk http://d-i.debian.org/daily-images/amd64/daily/build_hd-media_gtk.log * FAILED BUILD: armel Feb 27 06:07 buildd@ancina build_iop32x_netboot http://d-i.debian.org/daily-images/armel/daily/build_iop32x_netboot.log * FAILED BUILD: armel Feb 27 06:08 buildd@ancina build_iop32x_network-console_glantank http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_glantank.log * FAILED BUILD: armel Feb 27 06:09 buildd@ancina build_iop32x_network-console_n2100 http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_n2100.log * FAILED BUILD: armel Feb 27 06:10 buildd@ancina build_iop32x_network-console_ss4000e http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_ss4000e.log * FAILED BUILD: armel Feb 27 06:11 buildd@ancina build_kirkwood_netboot http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot.log * FAILED BUILD: armel Feb 27 06:12 buildd@ancina build_kirkwood_netboot-gtk http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot-gtk.log * FAILED BUILD: armel Feb 27 06:13 buildd@ancina build_kirkwood_network-console http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_network-console.log * FAILED BUILD: armel Feb 27 06:14 buildd@ancina build_orion5x_network-console http://d-i.debian.org/daily-images/armel/daily/build_orion5x_network-console.log * FAILED BUILD: armel Feb 27 06:15 buildd@ancina build_versatile_netboot http://d-i.debian.org/daily-images/armel/daily/build_versatile_netboot.log * FAILED BUILD: armel Feb 27 06:16 buildd@ancina build_ads_cf http://d-i.debian.org/daily-images/armel/daily/build_ads_cf.log * FAILED BUILD: i386 Feb 28 00:03 buildd@biber build_cdrom_isolinux http://d-i.debian.org/daily-images/i386/daily/build_cdrom_isolinux.log * FAILED BUILD: i386 Feb 28 00:04 buildd@biber build_cdrom_gtk http://d-i.debian.org/daily-images/i386/daily/build_cdrom_gtk.log * FAILED BUILD: i386 Feb 28 00:05 buildd@biber build_cdrom-xen http://d-i.debian.org/daily-images/i386/daily/build_cdrom-xen.log * FAILED BUILD: i386 Feb 28 00:05 buildd@biber build_netboot http://d-i.debian.org/daily-images/i386/daily/build_netboot.log * FAILED BUILD: i386 Feb 28 00:06 buildd@biber build_netboot-gtk http://d-i.debian.org/daily-images/i386/daily/build_netboot-gtk.log * FAILED BUILD: i386 Feb 28 00:07 buildd@biber build_netboot-xen http://d-i.debian.org/daily-images/i386/daily/build_netboot-xen.log * FAILED BUILD: i386 Feb 28 00:07 buildd@biber build_hd-media http://d-i.debian.org/daily-images/i386/daily/build_hd-media.log * FAILED BUILD: i386 Feb 28 00:08 buildd@biber build_hd-media_gtk http://d-i.debian.org/daily-images/i386/daily/build_hd-media_gtk.log * FAILED BUILD: ia64 Feb 28 00:13 buildd@alkman build_cdrom http://d-i.debian.org/daily-images/ia64/daily/build_cdrom.log * FAILED BUILD: ia64 Feb 28 00:14 buildd@alkman build_netboot http://d-i.debian.org/daily-images/ia64/daily/build_netboot.log * FAILED BUILD: mips Feb 28 00:22 buildd@lucatelli build_malta_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_malta_netboot-2.6.log * FAILED BUILD: mips Feb 28 00:24 buildd@lucatelli build_r4k-ip22_cdrom-2.6 http://d-i.debian.org/daily-images/mips/daily/build_r4k-ip22_cdrom-2.6.log * FAILED BUILD: mips Feb 28 00:26 buildd@lucatelli build_r4k-ip22_netboot-2.6 http://d-i.debian.
Bug#661501: debootstrap: Missing keyring file should abort with error
Package: debootstrap Version: 1.0.38 Severity: important Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, If the keyring file specified by a script with the keyring() function doesn't exist, debootstrap prints only warning but the installation continues. As the script clearly mentions the keyring and thus relies on its existence to verify the download, this should cause an error and abort the debootstrap installation. Otherwise a misconfiguration or incomplete installation (missing keyrings) can lead to download and installation of unverified packages. The following patch fixes this issue and aborts the installation: --- functions.orig 2012-02-27 18:42:58.0 +0100 +++ functions 2012-02-27 18:43:02.0 +0100 @@ -508,7 +508,7 @@ "$relsigdest" "$reldest" || true) | read_gpg_status progress 100 100 DOWNRELSIG "Downloading Release file signature" elif [ -z "$DISABLE_KEYRING" ] && [ -n "$KEYRING_WANTED" ]; then - warning KEYRING "Cannot check Release signature; keyring file not available %s" "$KEYRING_WANTED" + error 1 KEYRING "Cannot check Release signature; keyring file not available %s" "$KEYRING_WANTED" fi } I'm no debootstrap expert so I may be overlooking something here, if so please tell me. But I think --no-check-gpg already takes care of the case if no verification is required. Regards, Simon - -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages debootstrap depends on: ii wget 1.13.4-2 Versions of packages debootstrap recommends: ii debian-archive-keyring 2010.08.28 ii gnupg 1.4.11-3 debootstrap suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJPS8KlAAoJEJL+/bfkTDL5E4sP/0oOOVIENN7hmzhpkT3qw55W QNUMrVB/yNI8PXvrtDvcPIH4bqs+XB8wacUhgsuTpEtNbyrEAn1ej5V3kVjpuUGy m0fYyP7ak0JCQu2ZWDY8d99XPseskDJ3ZdJMAROw8SYTaATZ92zQ8DBe/1VHWIg9 P0o+lxDYvtiPb73sbOAtVRFGnu1YOBmeoAJHjk4/hBJ5I6ZzePRKKDoF0p8vrW3M r9BAaDVwxLrq75hqtrH0nV4GS19hgiWxo7EI6cuaAtyOdxO774AjN2YkydViPzid JP50dJAWbIow7DYF8cS1d+0JC3pWpKy+H9lG68/Q7f5E3D/IKW0mdOPwASYSUgzy ac64+Gio5r0WC+Y3XT4iilMms2Na7J2j0ZK7L1ZlpwVg1sFmH4aQUNqAUR6jb70T t25K4HqAkC1OtDf2Zha663Nu5TNiO3GgNn9AV+WB5mDauZZIzYAQWJ/JHMwvyYt6 x18TA1Umey1VeTdkcpbNhaM0qBom/HaO2fPlxDG9EEqKnUXAyhMQ5L2bQiOyiGGb iZnEImOa2e/TlzII0hcUX/36p7+ai0ydfhFcVLZRT754PRBmPOn2L/mDOQxRryPn QtxG888K9K91KnCif2dzOHT4Mejup7fVz0zKT1lLZoFpF3Nj2uj6+POTUw+/2Z59 s+E+OhWLTo9VcOe89tTi =G5Se -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120227175143.3155.25707.reportbug@nocreeps
Re: Planning for final lenny point release (5.0.10)
On Sat, Feb 25, 2012 at 10:12:11PM +0100, Philipp Kern wrote: > Hi, > > On Fri, Feb 24, 2012 at 08:44:46PM +, Adam D. Barratt wrote: > > Assuming the technical side still works, I do worry a little that a new > > DSA three weeks after the announced EOL for security support might > > confuse people. > > > > I suppose we could do a last-minute kernel update via o-p-u, although I > > don't know if we have any idea how many people actually upgrade to EOL > > point releases in the relatively short period before the move to > > archive.d.o. > > yeah, I wondered the same. I don't actually know when ftp-master gets > rid of oldstable on the mirrors. If we'd know that it's still around > for a few months I'd say o-p-u. The old suites used to stay on > security-master for ages, but AFAICS that's no longer the case > neither. > > Maybe the final announcement should point people at archive already > (it could already get synced there at that point, given that it won't > change anymore). Ok - sounds like no DSA, but maybe an upload via o-p-u. My vote is to do no kernel upload if the release gets scheduled for the first weekend in march - that's one week out, and I'll have spotty availability beginning mid-week. For later weekends, I'm for it. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120227011257.ga17...@dannf.org
