Bug#703146: #703146 release critical?
Quoting Christian PERRIER (bubu...@debian.org):
> > > This upload allows pbuilder to build a build chroot, so it seems fine,
> > > but, not being a wizard with debootstrap and archive stuff, I'd
> > > appreciate someone to confirm that fixing this is OK and fixing it the
> > > way it has been proposed in #703146 is OK too.
> >
> > a debdiff to the version in wheezy would have been nice :)
>
>
> Will do that.
>
>
>
debootstrap 1.0.47 has been uploaded with the attached debdiff
--
diff -Nru debootstrap-1.0.46/debian/changelog debootstrap-1.0.47/debian/changelog
--- debootstrap-1.0.46/debian/changelog 2012-12-27 15:51:54.0 +0100
+++ debootstrap-1.0.47/debian/changelog 2013-03-20 21:34:29.0 +0100
@@ -1,3 +1,15 @@
+debootstrap (1.0.47) unstable; urgency=low
+
+ * Team upload
+ * Properly decrypt the InRelease file when downloading from an archive
+where InRelease is used. This longstanding bug was masked by former
+APT behaviour and was revealed only with recent APT versions
+Closes: #703146
+Thanks to Michael Vogt for the analysis and patch
+ * Add a dependency on gpg because of the above change.
+
+ -- Christian Perrier Wed, 20 Mar 2013 21:34:29 +0100
+
debootstrap (1.0.46) unstable; urgency=low
* Team upload.
diff -Nru debootstrap-1.0.46/debian/control debootstrap-1.0.47/debian/control
--- debootstrap-1.0.46/debian/control 2012-12-27 14:42:50.0 +0100
+++ debootstrap-1.0.47/debian/control 2013-03-20 21:49:20.0 +0100
@@ -10,8 +10,8 @@
Package: debootstrap
Architecture: all
-Depends: ${misc:Depends}, wget
-Recommends: gnupg, ${keyring}
+Depends: ${misc:Depends}, wget, gnupg
+Recommends: ${keyring}
Description: Bootstrap a basic Debian system
debootstrap is used to create a Debian base system from scratch,
without requiring the availability of dpkg or apt. It does this by
diff -Nru debootstrap-1.0.46/functions debootstrap-1.0.47/functions
--- debootstrap-1.0.46/functions 2012-12-27 15:36:47.0 +0100
+++ debootstrap-1.0.47/functions 2013-03-20 21:30:41.0 +0100
@@ -530,7 +530,8 @@
warning KEYRING "Cannot check Release signature; keyring file not available %s" "$KEYRING_WANTED"
fi
if [ "$release_file_variant" = "IN" ]; then
- mv "$relsigdest" "$reldest"
+ rm -f $reldest
+gpg --output "$reldest" --decrypt --keyring "$KEYRING" --ignore-time-conflict "$relsigdest"
fi
}
signature.asc
Description: Digital signature
Bug#537535 didn't fix complete
hi all: I found bug#537535 didn't fix complete. When I add a installation interface use db_capb escape, the interface didn't display, when I comment out this line interface is appear, but '\n' is not escape. In my program I use: db_subst test/num DEV "$dev", and $dev have '\n' in it, this '\n' didn't escape normal. I use debian-testing-amd64-CD-1.iso which generate at 2013-03-18. And I found cdebconf-udeb_0.175_amd64.udeb didn't contain debconf-escape program. -- Best Regards, Bo Qin
Bug#703404: debootstrap wheezy Release InRelease error
Apparently not the same as #703146, since I still get the same error (busybox cannot be authenticated, installation of the base system failed) when trying to install wheezy with a new net-install stick, with every mirror I try. -- Tomas Chmiel 06.70.47.98.27 Développeur réseaux & Bases de Données chez Caldera Graphics ( http://www.caldera.com) Associé - Administrateur Systèmes et Réseaux chez L'offreWeb ( http://www.loffreweb.com) Autoentrepreneur - Administration systèmes et réseaux, Hébergements - http://www.strasdev.com
Bug#703404: debootstrap wheezy Release InRelease error
On 03/22/2013 07:03 AM, Christian PERRIER wrote: Quoting Sebastian Bengtsson (sebastian.bengts...@openend.se): So this is my theory: At some point a debootstrap.invalid_dists_wheezy_InRelease is downloaded form the repository InRelease file. It is then renamed to debootstrap.invalid_dists_wheezy_Release with signature intact, and that is in turn renamed to cdn.debian.net_debian_dists_wheezy_Release. So, in short, this bug is the same than #703146 which I should soon fix with an upload? Well the Release/InRelease thing is an apparent error here. It might be that that transition causes similar problems in other parts (??base-installer??). I guess I do not know that #703146 is the cause of the busybox problem common to reporters in this bug. It just seems likely that the authentication error is connected with a messed up Release file. I am experiencing this error from the debian installer that which talks about base-installer and debootstrap. See relevant part of syslog attached. Regards, Sebastian Bengtsson Mar 22 12:48:02 debootstrap: Setting up udev (175-7.1) ... Mar 22 12:48:03 debootstrap: A chroot environment has been detected, udev not started. Mar 22 12:48:03 debootstrap: Setting up iptables (1.4.14-3.1) ... Mar 22 12:48:03 debootstrap: Setting up man-db (2.6.2-1) ... Mar 22 12:48:04 debootstrap: Building database of manual pages ... Mar 22 12:48:13 debootstrap: Setting up apt (0.9.7.8) ... Mar 22 12:48:13 debootstrap: gpg: Mar 22 12:48:13 debootstrap: keyring `/etc/apt/trusted.gpg' created Mar 22 12:48:13 debootstrap: gpg: Mar 22 12:48:13 debootstrap: key B98321F9: "Squeeze Stable Release Key " no t changed Mar 22 12:48:13 debootstrap: gpg: Mar 22 12:48:13 debootstrap: key 473041FA: "Debian Archive Automatic Signing Key (6.0/squeeze) " not changed Mar 22 12:48:13 debootstrap: gpg: Mar 22 12:48:13 debootstrap: key 65FFB764: "Wheezy Stable Release Key " not changed Mar 22 12:48:13 debootstrap: gpg: Mar 22 12:48:13 debootstrap: key 46925553: "Debian Archive Automatic Signing Key (7.0/wheezy) " not changed Mar 22 12:48:13 debootstrap: gpg: Mar 22 12:48:13 debootstrap: Total number processed: 4 Mar 22 12:48:13 debootstrap: gpg: Mar 22 12:48:13 debootstrap: unchanged: 4 Mar 22 12:48:13 debootstrap: gpg: Mar 22 12:48:13 debootstrap: /etc/apt//trustdb.gpg: trustdb created Mar 22 12:48:13 debootstrap: Setting up wget (1.13.4-3) ... Mar 22 12:48:13 debootstrap: Setting up libcwidget3 (0.5.16-3.4) ... Mar 22 12:48:13 debootstrap: Setting up aptitude (0.6.8.2-1) ... Mar 22 12:48:14 debootstrap: update-alternatives: Mar 22 12:48:14 debootstrap: using /usr/bin/aptitude-curses to provide /usr/bin/aptitude (aptitude) in auto mode Mar 22 12:48:14 debootstrap: Mar 22 12:48:14 debootstrap: Setting up tasksel (3.14+nmu1) ... Mar 22 12:48:14 debootstrap: Setting up tasksel-data (3.14+nmu1) ... Mar 22 12:48:16 apt-install: Queueing package keyboard-configuration for later installation Mar 22 12:48:16 apt-install: Queueing package console-setup for later installation Mar 22 12:48:16 base-installer: Get:1 http://ftp.de.debian.org wheezy Release.gpg [836 B] Mar 22 12:48:16 base-installer: Hit http://ftp.de.debian.org wheezy Release Mar 22 12:48:16 base-installer: Ign http://ftp.de.debian.org wheezy Release Mar 22 12:48:16 base-installer: Get:2 http://ftp.de.debian.org wheezy/main amd64 Packages/DiffIndex [7876 B] Mar 22 12:48:16 base-installer: Get:3 http://ftp.de.debian.org wheezy/main Translation-en [3857 kB] Mar 22 12:48:18 base-installer: Fetched 3866 kB in 1s (1952 kB/s) Mar 22 12:48:18 base-installer: Reading package lists... Mar 22 12:48:19 base-installer: Mar 22 12:48:19 base-installer: W Mar 22 12:48:19 base-installer: : Mar 22 12:48:19 base-installer: GPG error: http://ftp.de.debian.org wheezy Release: The following signatures were invalid: BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key (6.0/squeeze) Mar 22 12:48:19 base-installer: Mar 22 12:48:19 in-target: Reading package lists... Mar 22 12:48:19 in-target: Mar 22 12:48:19 in-target: Building dependency tree... Mar 22 12:48:19 in-target: Mar 22 12:48:19 in-target: The following NEW packages will be installed: Mar 22 12:48:19 in-target: locales Mar 22 12:48:19 in-target: 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Mar 22 12:48:19 in-target: Need to get 5712 kB of archives. Mar 22 12:48:19 in-target: After this operation, 15.5 MB of additional disk space will be used. Mar 22 12:48:19 in-target: WARNING: The following packages cannot be authenticated! Mar 22 12:48:19 in-target: locales Mar 22 12:48:19 in-target: E Mar 22 12:48:19 in-target: : Mar 22 12:48:19 in-target: There are problems and -y was used without --force-yes Mar 22 12:48:19 in-target: Mar 22 12:48:19 localechooser: error: the command 'validlocale' is not available Mar 22 12:48:20 base-installer: info: kernel linux-image-rt-amd64 usable on em64t-p4 Mar 22 12:48:20 base-installer: info: kernel l
Error installing wheezy due to bad GPG signatures(?) on ftp.sk.debian.org
Hi, apologies for the cross-posting, I'm not sure where to send this to catch people's attention. I've just tried to install wheezy using the d-i RC1 images on a GlobalScale DreamPlug (Marvell kirkwood, armel). The installer failed while installing the base system, with the following in syslog: --- Mar 22 17:42:39 debootstrap: Setting up apt (0.9.7.8) ... Mar 22 17:42:43 debootstrap: gpg: Mar 22 17:42:43 debootstrap: keyring `/etc/apt/trusted.gpg' created Mar 22 17:42:43 debootstrap: gpg: Mar 22 17:42:43 debootstrap: key B98321F9: "Squeeze Stable Release Key " not changed Mar 22 17:42:43 debootstrap: gpg: Mar 22 17:42:43 debootstrap: key 473041FA: "Debian Archive Automatic Signing Key (6.0/sque eze) " not changed Mar 22 17:42:43 debootstrap: gpg: Mar 22 17:42:43 debootstrap: key 65FFB764: "Wheezy Stable Release Key " not changed Mar 22 17:42:43 debootstrap: gpg: Mar 22 17:42:43 debootstrap: key 46925553: "Debian Archive Automatic Signing Key (7.0/whee zy) " not changed Mar 22 17:42:43 debootstrap: gpg: Mar 22 17:42:43 debootstrap: Total number processed: 4 Mar 22 17:42:43 debootstrap: gpg: Mar 22 17:42:43 debootstrap: unchanged: 4 Mar 22 17:42:43 debootstrap: gpg: Mar 22 17:42:43 debootstrap: /etc/apt//trustdb.gpg: trustdb created Mar 22 17:42:44 debootstrap: Setting up wget (1.13.4-3) ... Mar 22 17:42:47 debootstrap: Setting up libcwidget3 (0.5.16-3.4) ... Mar 22 17:42:50 debootstrap: Setting up aptitude (0.6.8.2-1) ... Mar 22 17:42:53 debootstrap: update-alternatives: Mar 22 17:42:53 debootstrap: using /usr/bin/aptitude-curses to provide /usr/bin/aptitude (aptitude) in auto mode Mar 22 17:42:53 debootstrap: Mar 22 17:42:54 debootstrap: Setting up tasksel (3.14+nmu1) ... Mar 22 17:42:59 debootstrap: Setting up tasksel-data (3.14+nmu1) ... Mar 22 17:43:05 base-installer: Get:1 http://ftp.sk.debian.org wheezy Release.gpg [836 B] Mar 22 17:43:06 base-installer: Hit http://ftp.sk.debian.org wheezy Release Mar 22 17:43:06 base-installer: Ign http://ftp.sk.debian.org wheezy Release Mar 22 17:43:06 base-installer: Get:2 http://ftp.sk.debian.org wheezy/main armel Packages/DiffIndex [7876 B] Mar 22 17:43:06 base-installer: Get:3 http://ftp.sk.debian.org wheezy/main Translation-en [3857 kB] Mar 22 17:43:21 base-installer: Fetched 3866 kB in 15s (246 kB/s) Mar 22 17:43:21 base-installer: Reading package lists... Mar 22 17:43:52 base-installer: Mar 22 17:43:52 base-installer: W: GPG error: http://ftp.sk.debian.org wheezy Release: The following signatures were invalid: BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key (6.0/squeeze) Mar 22 17:43:54 in-target: Reading package lists... Mar 22 17:43:54 in-target: Mar 22 17:43:54 in-target: Building dependency tree... Mar 22 17:43:55 in-target: Mar 22 17:43:56 in-target: The following NEW packages will be installed: Mar 22 17:43:56 in-target: locales Mar 22 17:43:56 in-target: 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Mar 22 17:43:56 in-target: Need to get 5712 kB of archives. Mar 22 17:43:56 in-target: After this operation, 15.5 MB of additional disk space will be used. Mar 22 17:43:56 in-target: WARNING: The following packages cannot be authenticated! Mar 22 17:43:56 in-target: locales Mar 22 17:43:56 in-target: E: There are problems and -y was used without --force-yes Mar 22 17:43:57 localechooser: error: the command 'validlocale' is not available --- I'm not sure if this is a problem with d-i, the Slovak mirror, or both. Could someone in the know please check what is going on? Should I file a bug report for this? In the mean time I will try re-running the installer with a different mirror to see if anything changes. -mato signature.asc Description: Digital signature
Re: Error installing wheezy due to bad GPG signatures(?) on ftp.sk.debian.org
Quoting Martin Lucina (mar...@lucina.net): > Hi, > > apologies for the cross-posting, I'm not sure where to send this to catch > people's attention. This is bug #703146. signature.asc Description: Digital signature
d-i for wheezy on a Dreamplug, docs/recommended practice?
Hi, having found some time to play with a Dreamplug I've given a go at installing wheezy using the d-i RC1 images. Got hit by #703146, but that is a separate problem (presumably d-i nightlies in the next few days will pick up the fixed debootstrap?). Anyhow, my question / offer to help is: AFAICS at the moment there is no real documentation on how joe user can install wheezy on their Dreamplug using d-i, or if there is I haven't found it. In my case, being vaguely familiar with U-boot (and having just flashed U-boot 2013.01.01 on the plug), I followed these steps: 1. Download uImage and uInitrd from [1]. http://ftp.nl.debian.org/debian/dists/testing/main/installer-armel/current/images/. 2. Copy both to a (FAT-formatted) USB stick. 3. Boot into U-boot, stop the autoboot and run the following commands: usb start usb tree [determine, using "fatls" etc, which device is the usb stick] setenv bootargs console=ttyS0,115200 fatload usb 2:1 0x640 uImage fatload usb 2:1 0x800 uInitrd bootm 0x640 0x800 Who can I contact about getting these steps into the wheezy installation guide in some prominent place? Futher: What is a user w/o a JTAG device to do? How is he/she supposed to run the installer? Further #2: All of the instructions I've found on the net about upgrading U-boot discuss either using OpenOCD (which is unreliable as hell, I never managed to make it work due to timing problems), or using an existing U-boot to load the new image and flash it. There is another method which is not mentioned anywhere(!!) which I use and is 100% reliable, namely booting over UART using kwuartboot [2], loading the new image also over UART using e.g. kermit and then flashing it. Would it be worthwhile to document this somewhere? If so, where? Obviously this only works for people with the JTAG unit/some other compatible UART level converter. Best, -mato [1] http://ftp.nl.debian.org/debian/dists/testing/main/installer-armel/current/images/ [2] http://www.solinno.co.uk/public/kwuartboot/ signature.asc Description: Digital signature
Bug#703661: Acknowledgement (installation-reports: Unable to complete partitioning with RAID + LVM + encryption after forgetting a partition)
My initial report was actually optimistic: running fdisk and deleting the partition tables does not allow the install to finish. Even after doing this and zeroing both disks, the partitioning screen shows a RAID1 device, LVM volume group, and encrypted volume that it won't let me delete. -- 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/514ce4fc@eff.org
Re: d-i for wheezy on a Dreamplug, docs/recommended practice?
Le Fri, Mar 22, 2013 at 07:42:26PM +0100, Martin Lucina a écrit : > > Anyhow, my question / offer to help is: AFAICS at the moment there is no > real documentation on how joe user can install wheezy on their Dreamplug > using d-i, or if there is I haven't found it. > > In my case, being vaguely familiar with U-boot (and having just flashed > U-boot 2013.01.01 on the plug), I followed these steps: > > 1. Download uImage and uInitrd from [1]. > > http://ftp.nl.debian.org/debian/dists/testing/main/installer-armel/current/images/. > 2. Copy both to a (FAT-formatted) USB stick. > 3. Boot into U-boot, stop the autoboot and run the following commands: > > usb start > usb tree > [determine, using "fatls" etc, which device is the usb stick] > setenv bootargs console=ttyS0,115200 > fatload usb 2:1 0x640 uImage > fatload usb 2:1 0x800 uInitrd > bootm 0x640 0x800 > > Who can I contact about getting these steps into the wheezy installation > guide in some prominent place? Dear Martin, thanks for your input. The installation guide is packaged, so you can make your suggestion and send a patch through a bug report against the "installation-guide" package (which will be received on the "debian-boot" mailing list). As you figured out by yourself, the "debian-arm" mailing list is also a good place for discussing the additions that you propose. Have a nice week-end, -- Charles Plessy Tsurumi, Kanagawa, Japan -- 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/20130323001744.ga30...@falafel.plessy.net
Re: d-i for wheezy on a Dreamplug, docs/recommended practice?
Hi Martin, On 2013-03-22 18:42, Martin Lucina wrote: [...] Futher: What is a user w/o a JTAG device to do? How is he/she supposed to run the installer? I don't think it's possible. The only other way to get a new distro on the device would be to write a pre-created image on to a MicroSD card and take it apart to install it. Further #2: All of the instructions I've found on the net about upgrading U-boot discuss either using OpenOCD (which is unreliable as hell, I never managed to make it work due to timing problems), or using an existing U-boot to load the new image and flash it. I have to agree on this point: I could never get OpenOCD to work on either of my two Dreamplugs. There is another method which is not mentioned anywhere(!!) which I use and is 100% reliable, namely booting over UART using kwuartboot [2], loading the new image also over UART using e.g. kermit and then flashing it. Would it be worthwhile to document this somewhere? If so, where? Obviously this only works for people with the JTAG unit/some other compatible UART level converter. Since I wrote that, a better version[1] called kwboot (although I think the name may be about to change) has been independently written and incorporated into the u-boot source code. Your point about providing instructions to help people get things up and running still stands of course. I shall make a small start on that by pointing to kwboot from my webpage. Regards, Leigh. [1] http://forum.doozan.com/read.php?3,7852,7852 -- 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/b8847baaffc5c2909881e45137b15...@doppler.thel33t.co.uk
Bug#703747: netcfg: preseed netcfg: confusion or regression about disable_dhcp, disable_autoconfig and use_autoconfig
Package: netcfg Version: 1.106 Severity: normal Tags: d-i Dear Maintainer, * What led up to the situation? I have built a preseed.cfg file to perform an automated installation on a remote Virtual Machine with a static IP address. The original iso image was downloaded from: http://ftp.debian.org/debian/dists/wheezy/main/installer- amd64/current/images/netboot/mini.iso [built on 20130211] Then the iso image has been rebuild with a custom initrd including the preseed.cfg file at its root, with: [...] # gunzip initrd.gz # ls preseed.cfg | cpio --create --append --format newc --file initrd # gzip --best initrd [...] # genisoimage [...] I'm not an expert nor a wizard of preseeding, but enough familiar with this technique to read and understand documentation. First of all, I have read this page: http://www.debian.org/devel/debian-installer/News/2013/20130217 where it is explicitly said: 'Use netcfg/disable_autoconfig instead of netcfg/disable_dhcp (#689531).' This is confirmed by: http://lists.debian.org/debian-boot/2012/10/msg00054.html http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689531#25 and even /var/lib/dpkg/info/netcfg.templates in the initrd of the installer. But with: d-i netcfg/disable_autoconfig boolean true netcfg still try DHCP first, and installation fails. * What exactly did you do (or not do) that was effective (or ineffective)? I don't own an amd64 PC, so I have performed other tests with my i386 laptop. I have played with several sets of configuration in preseed.cfg or on boot command line, with the following, surprising results: d-i netcfg/disable_autoconfig boolean true -> doesn't work d-i netcfg/use_autoconfig boolean false -> doesn't work d-i netcfg/disable_autoconfig boolean true d-i netcfg/use_autoconfig boolean false -> doesn't work on boot cmdline: netcfg/disable_autoconfig=true netcfg/use_autoconfig=false -> doesn't work But with the official mini.iso (the same as above but for i386), without preseed.cfg or whatever, just on boot command line of the default menu entry: netcfg/disable_dhcp -> leads me directly to the configuration of a static IP Now, if I put this in a preseed.cfg: d-i netcfg/disable_dhcp boolean true d-i netcfg/get_ipaddress string 192.168.1.86/24 d-i netcfg/get_gateway string 192.168.1.1 d-i netcfg/get_nameservers string 192.168.1.1 it works like a charm So, what about netcfg/use_autoconfig and netcfg/disable_autoconfig ? Or what about the documentation ? I don't understand. The version of netcfg shipped in the downloaded mini.iso is 1.106; there was a bugreport against the same program, version 1.92, to say that d-i netcfg/disable_dhcp boolean true fails [1]. Is 1.106 a regression ? Now, to build a generic preseed.cfg file that could work with different versions of the installer, and to be sure DHCP config is skipped, I use: d-i netcfg/disable_dhcp boolean true d-i netcfg/disable_autoconfig boolean true d-i netcfg/use_autoconfig boolean false knowing that at least one of them (and probably two) is useless; but how to know which, in advance... cheers, quidame [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688273 -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-proposed-updates') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-486 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20130323010014.8865.70633.reportbug@debian
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * OLD BUILD:kfreebsd-amd64 Mar 21 00:35 buildd@fano build_cdrom_grub http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom_grub.log * OLD BUILD:kfreebsd-amd64 Mar 21 00:35 buildd@fano build_cdrom_gtk http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom_gtk.log * OLD BUILD:kfreebsd-amd64 Mar 21 00:37 buildd@fano build_netboot http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log * OLD BUILD:kfreebsd-amd64 Mar 21 00:39 buildd@fano build_netboot-9 http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-9.log * OLD BUILD:kfreebsd-amd64 Mar 21 00:43 buildd@fano build_netboot-gtk http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-gtk.log * OLD BUILD:kfreebsd-amd64 Mar 21 00:46 buildd@fano build_netboot-gtk-9 http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-gtk-9.log Totals: 100 builds (0 failed, 6 old) -- 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/e1ujcov-00046b...@ravel.debian.org
