kfreebsd-{amd64|i386} D-I daily build failures
This mail is a small up mail to mention that I'm still monitoring the daily reports of the daily buils aggregator. There's always something that's going wrong so the task is harder...even harder because I do this offline and can't immediately check logs Anyway. We have a few build failures on some exotic targets for a few architectures, which I don't really investigate. I'd expect people interested deeply in those architectures and more able than me to understand what is an orion5_network-console or r4k-ip22_cdrom image, to look more closely. ot sure it happens, though. Still, I would like to point out that come common kfreebsd-amd64 daily builds seem to be failing (particularly the netboot ones which is always an indication of a pontetially annoying breakage): * FAILED BUILD: kfreebsd-amd64 May 06 00:11 buildd@fano build_cdrom http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom.log * FAILED BUILD: kfreebsd-amd64 May 06 00:11 buildd@fano build_netboot http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log * FAILED BUILD: kfreebsd-i386 May 06 00:11 buildd@finzi build_cdrom http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_cdrom.log * FAILED BUILD: kfreebsd-i386 May 06 00:11 buildd@finzi build_netboot http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot.log Quoting Daily build aggregator (debian-boot@lists.debian.org): Debian installer build overview --- Failed or old builds: * FAILED BUILD: armel May 05 18:05 joey@box build_orion5x_network-console http://people.debian.org/~joeyh/d-i/armel/images/daily/build_orion5x_network-console.log * FAILED BUILD: kfreebsd-amd64 May 06 00:11 buildd@fano build_cdrom http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom.log * FAILED BUILD: kfreebsd-amd64 May 06 00:11 buildd@fano build_netboot http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log * FAILED BUILD: kfreebsd-i386 May 06 00:11 buildd@finzi build_cdrom http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_cdrom.log * FAILED BUILD: kfreebsd-i386 May 06 00:11 buildd@finzi build_netboot http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot.log * OLD BUILD:mips Apr 20 00:19 buildd@ball build_malta_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_malta_netboot-2.6.log * OLD BUILD:mips Apr 20 00:23 buildd@ball build_r4k-ip22_cdrom-2.6 http://d-i.debian.org/daily-images/mips/daily/build_r4k-ip22_cdrom-2.6.log * OLD BUILD:mips Apr 20 00:27 buildd@ball build_r4k-ip22_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_r4k-ip22_netboot-2.6.log * OLD BUILD:mips Apr 20 00:32 buildd@ball build_r5k-ip32_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_r5k-ip32_netboot-2.6.log * OLD BUILD:mips Apr 20 00:37 buildd@ball build_sb1-bcm91250a_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_sb1-bcm91250a_netboot-2.6.log * OLD BUILD:mips Apr 20 00:38 buildd@ball build_miniiso http://d-i.debian.org/daily-images/mips/daily/build_miniiso.log * OLD BUILD:s390 May 01 00:03 buildd@zandonai build_generic http://d-i.debian.org/daily-images/s390/daily/build_generic.log * OLD BUILD:s390 May 01 00:03 buildd@zandonai build_tape http://d-i.debian.org/daily-images/s390/daily/build_tape.log * FAILED BUILD: amd64 May 05 22:49 debian-cd@pettersson 2sidmips http://cdbuilder.debian.org/cdimage-log/2sidmips * FAILED BUILD: amd64 May 05 22:49 debian-cd@pettersson 1wheezymips http://cdbuilder.debian.org/cdimage-log/1wheezymips * FAILED BUILD: amd64 May 05 22:49 debian-cd@pettersson 2wheezymips http://cdbuilder.debian.org/cdimage-log/2wheezymips * FAILED BUILD: amd64 May 05 22:49 debian-cd@pettersson 1sidmips http://cdbuilder.debian.org/cdimage-log/1sidmips * FAILED BUILD: amd64 May 05 22:57 debian-cd@pettersson 1sidkfreebsd-amd64 http://cdbuilder.debian.org/cdimage-log/1sidkfreebsd-amd64 * FAILED BUILD: amd64 May 05 22:57 debian-cd@pettersson 2sidkfreebsd-amd64 http://cdbuilder.debian.org/cdimage-log/2sidkfreebsd-amd64 * FAILED BUILD: amd64 May 05 22:58 debian-cd@pettersson 1sidkfreebsd-i386 http://cdbuilder.debian.org/cdimage-log/1sidkfreebsd-i386 * FAILED BUILD: amd64 May 05 22:59 debian-cd@pettersson 2sidkfreebsd-i386 http://cdbuilder.debian.org/cdimage-log/2sidkfreebsd-i386 Totals: 89 builds (13 failed, 8 old) -- To UNSUBSCRIBE, email to
Re: kfreebsd-{amd64|i386} D-I daily build failures
Le 06/05/2011 06:40, Christian PERRIER a écrit : This mail is a small up mail to mention that I'm still monitoring the daily reports of the daily buils aggregator. There's always something that's going wrong so the task is harder...even harder because I do this offline and can't immediately check logs Anyway. We have a few build failures on some exotic targets for a few architectures, which I don't really investigate. I'd expect people interested deeply in those architectures and more able than me to understand what is an orion5_network-console or r4k-ip22_cdrom image, to look more closely. ot sure it happens, though. Still, I would like to point out that come common kfreebsd-amd64 daily builds seem to be failing (particularly the netboot ones which is always an indication of a pontetially annoying breakage): * FAILED BUILD: kfreebsd-amd64 May 06 00:11 buildd@fano build_cdrom http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom.log * FAILED BUILD: kfreebsd-amd64 May 06 00:11 buildd@fano build_netboot http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log * FAILED BUILD: kfreebsd-i386 May 06 00:11 buildd@finzi build_cdrom http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_cdrom.log * FAILED BUILD: kfreebsd-i386 May 06 00:11 buildd@finzi build_netboot http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot.log This is due to the current perl transition, debiandoc-sgml is not installable anymore, probably until all packages get binNMUed. -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- 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/4dc39dcb.8000...@aurel32.net
Bug#113567: marked as done (busybox-static: busybox as login shell and ash)
Your message dated Fri, 06 May 2011 15:13:59 +0400 with message-id 4dc3d7f7.6040...@msgid.tls.msk.ru and subject line Re: Bug#113567: busybox-static: busybox as login shell and ash has caused the Debian Bug report #113567, regarding busybox-static: busybox as login shell and ash to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 113567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=113567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: busybox-static Version: 1:0.60.1-2 Severity: wishlist If you want to have busybox as your root login shell (its shell has been far better than sash for some time now), you can simply make a symlink to it from either sh or ash. Clearly busybox would make a dumb choice for the former, and I have the latter installed already. Please add another shell alias to busybox, maybe busysh or something? That'd make it play nicely with ash and still make it able to be root's login shell. -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux galen 2.4.8-ac8 #1 Tue Aug 21 06:45:59 PDT 2001 i686 Locale: LANG=en_US, LC_CTYPE=en_US -- Joseph Carter knght...@bluecherry.netFree software developer 2.3.1 has been released. Folks new to this game should remember that 2.3.* releases are development kernels, with no guarantees that they will not cause your system to do horrible things like corrupt its disks, catch fire, or start running Mindcraft benchmarks. -- Slashdot pgphorM8CExiA.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Version: 1:1.17.1-8 [Replying to a bug which is about 10 years old...] 26.09.2001 12:54, Joseph Carter wrote: Package: busybox-static Version: 1:0.60.1-2 Severity: wishlist If you want to have busybox as your root login shell (its shell has been far better than sash for some time now), you can simply make a symlink to it from either sh or ash. Clearly busybox would make a dumb choice for the former, and I have the latter installed already. Please add another shell alias to busybox, maybe busysh or something? That'd make it play nicely with ash and still make it able to be root's login shell. Several Debian revisions back (in lenny? etch?), ash package has been replaced with dash. There's still a compatibility/ transitional package ash, wich provides /bin/ash symlink to dash, but it's obviously optional. So I think this bugreport is not relevant anymore, so closing it finally, after about 10 years since original bugreport. Thanks! /mjt ---End Message---
CONFIG_NLS=y in 2.6.39 packages (Was Re: [PATCH base-installer] Update i386 kernel selection for new flavours in wheezy)
On Fri, 2011-04-29 at 09:53 +0100, Ian Campbell wrote: On Fri, 2011-04-29 at 05:03 +0100, Ben Hutchings wrote: On Thu, 2011-04-28 at 08:38 +0100, Ian Campbell wrote: On Sun, 2011-04-24 at 15:59 +0100, Ben Hutchings wrote: The '686-bigmem' flavour will be renamed to '686-pae'; support both names. The '686' flavour will be removed, but we can still offer it if available. Do you also have patches for d-i's kernel-wedge and the main installer build? No, I'm not familiar with those. I did the kernel installation selection myself because I've worked on it before. Also debian-cd will need changes too. Since the latter two are mainly due to Xen support I can take care of that if you like, although I think it will depend on the kernel actually being uploaded since I can't see an easy way to support both names in the main installer build. So it depends on when the d-i team decides to switch to 2.6.39 (or later). But you can get your patches ready before then. Correct. I'll look into it. While I was hacking up an updated kernel-wedge/linux-kernel-di-i386-2.6 to use 2.6.39 to test this I noticed that nls_base is now built in instead of modular, despite CONFIG_NLS=m under debian/config. This is because various =y options (e.g. CONFIG_PCI_LABEL, CONFIG_JOLIET) now appear to select NLS... Probably not a big deal, nls_base.o is ~5k, but thought I'd mention it. It just means that the nls-core-modules udeb goes away. Ian. -- Ian Campbell Current Noise: Napalm Death - De-evolution Ad Nauseum I couldn't possibly fail to disagree with you less. -- 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/1304685363.26692.155.ca...@zakaz.uk.xensource.com
Bug#375568: busybox-static should include Provides: busybox
Replying to an old bugreport... 15.01.2008 01:03, Jameson Rollins wrote: Hello. I would like to get an update on the status of this bug. Right now, busybox-static is basically uninstallable on any system that needs initramfs-tools, which I imagine is most. The proposed solution would work, ie. set Provides: busybox. I would really like to use this tool but can't at the moment. I'd like to let the two packages co-exist with each other instead of conflicting. I'm not sure for now how to achieve this. Merely Providing busybox in busybox-static, while should work, is wrong IMHO, because the two are used for different purposes, and it's not wise to replace bb in initramfs with busybox-static just by installing -static flavour. Also, no one (I think) tested -static build in initramfs, and I'm not sure it will ever work... ;) Maybe it's a good idea to install it as /bin/busybox-static instead of /bin/busybox, and provide a symlink named /bin/busybox in case regular busybox package is not installed. At least, for that busybox-static needs to recognize its new other name. Also, busybox-static first need to provide at least the applets/features regular build provides already. I checked the config difference today and hopefully enabled missing parts of -static config which were found in regular config, so this should be fixed now. Currently, busybox is actually not _required_ in initramfs (but initramfs is better - like more powerful - with it). So maybe it's not that problematic anymore. But it's still an issue, obviously, which needs a solution. Thanks! /mjt -- 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/4dc3fdee.8010...@bk.ru
Bug#375568: busybox-static should include Provides: busybox
On Fri, May 06, 2011 at 05:55:58PM +0400, Michael Tokarev wrote: 15.01.2008 01:03, Jameson Rollins wrote: Hello. I would like to get an update on the status of this bug. Right now, busybox-static is basically uninstallable on any system that needs initramfs-tools, which I imagine is most. The proposed solution would work, ie. set Provides: busybox. I would really like to use this tool but can't at the moment. initramfs-tools does not depend on busybox. I'd like to let the two packages co-exist with each other instead of conflicting. I'm not sure for now how to achieve this. Why? Merely Providing busybox in busybox-static, while should work, is wrong IMHO, because the two are used for different purposes, and it's not wise to replace bb in initramfs with busybox-static just by installing -static flavour. Also, no one (I think) tested -static build in initramfs, and I'm not sure it will ever work... ;) They are used for the same purpose, one tool. Bastian -- 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/20110506140929.ga7...@wavehammer.waldi.eu.org
Bug#375568: busybox-static should include Provides: busybox
06.05.2011 18:09, Bastian Blank wrpte: On Fri, May 06, 2011 at 05:55:58PM +0400, Michael Tokarev wrote: 15.01.2008 01:03, Jameson Rollins wrote: Hello. I would like to get an update on the status of this bug. Right now, busybox-static is basically uninstallable on any system that needs initramfs-tools, which I imagine is most. The proposed solution would work, ie. set Provides: busybox. I would really like to use this tool but can't at the moment. initramfs-tools does not depend on busybox. initramfs-tools does not depend on busybox indeed, but it recommends busybox|busybox-initramfs. With default apt settings that basically translates to depends, since all Recommends are installed too. I'd like to let the two packages co-exist with each other instead of conflicting. I'm not sure for now how to achieve this. Why? Merely Providing busybox in busybox-static, while should work, is wrong IMHO, because the two are used for different purposes, and it's not wise to replace bb in initramfs with busybox-static just by installing -static flavour. Also, no one (I think) tested -static build in initramfs, and I'm not sure it will ever work... ;) They are used for the same purpose, one tool. No, the purpose is actually different. And for added fun, I for one do NOT know the purpose of busybox-static, why people use it for in reality, except of several somewhat obscure cases. Regular busybox build is used for initramfs (to enhance it with some rescue abilities if nothing else) and for other regular tasks - like small dhcp client, like one or two utils which sometimes aren't installed but busybox provides and the like. There, regular busybox is the way to go really - with shared regular glibc. For static busybox, the usage question is more interesting. Long time ago, especially when there was libc5 = libc6 transition, I wanted to have some tool like busybox, statically linked to be independent of any current library mess, so that it's possible to fix a broken system after some unsuccessful libc6 install/upgrade, -- live, without rebooting. So at least one potential usage is to have busybox-static floating around somewhere just in case it will be needed someday, when everything else fails. That's completely different scenario. As of using busybox-static in initramfs instead of regular busybox - we already have 2 libc in initramfs, it's already too much, there's no need to have THREE of them in there. I mean, klibc, regular glibc for stuff like mdadm, cryptoloop and other things which uses glibc, and also glibc statically linked into busybox. (There, I'd offer a choice - use glibc OR klibc, instead of klibc or (klibc+glibc), but that's different issue entirely). One possibility is to have busybox-static install into /sbin instead of /bin. That goes on-par with the usage example I outlined above, sort of, but is a bit ugly too. /mjt -- 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/4dc41a3e.50...@msgid.tls.msk.ru
Preseeded d-i image doesn't boot from USB anymore
Morning d-iers First and foremost thanks a lot for your amazing work on d-i! I use Debian since years and the installation is always fantastically easy. A few weeks ago I started to work with d-i's preseedeing capabilities and after finding a nice way (or better a description in the debian wiki [1]) to regenerate the debian ISO image with the new preseeded installer a problem appeared for me which I couldn't solve. Neither by finding a solution in the debian wiki, with Google or nor by reading the debian installation manual. To regenerate the debian ISO I use the attached script (modified from [1]) and here is a short extract of the included commands: ### mkdir /tmp/loop mount -o loop $1 /tmp/loop mkdir /tmp/cd rsync -a -H --exclude=TRANS.TBL /tmp/loop/ /tmp/cd/ umount /tmp/loop mkdir irmod cd irmod gzip -d /tmp/cd/install.386/initrd.gz | cpio --extract --verbose --make- directories --no-absolute-filenames cp $2 preseed.cfg find . | cpio -H newc --create --verbose | gzip -9 /tmp/cd/install.386/initrd.gz cd ../ rm -rf /tmp/irmod genisoimage -o test.iso -r -J -no-emul-boot -boot-load-size 4 -boot-info-table -b isolinux/isolinux.bin -c isolinux/boot.cat . ### $1 is the used Debian testing ISO and $2 the preseeding file. When I test this generated image in Virtual box it works flawlessly. But when I copy the image to a USB stick (with every of the 3 in the installation manual described methods) it doesn't boot on any PC I've tried (at least three different). When I copy the unmodified Debian image to a USB stick it works. So where is the problem? I'm thankful for every hint. Thx a lot for any help Mario [1] http://wiki.debian.org/DebianInstaller/Preseed/EditIso makepreiso.sh Description: application/shellscript
Bug#625890: testing install report
Package: installation-reports Boot method: netinst-iso Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso Date: 20110506-10:15am PST Machine: VirtualBox OSE 4.0.4 Processor: Memory: Partitions: Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O ] Detect network card:[ ] Configure network: [ ] Detect CD: [ O] Load installer modules: [O ] Detect hard drives: [ O] Partition hard drives: [ O] Install base system:[ E ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: during Install Basic System -- Warning: Failure trying to run: chroot /target dpkg --force-depends --install /var/cache/apt/archives/base_files_6.3_i386.deb Everything was very smooth up to this point. This is the first installation error I've ever encountered with Debian. -- Member in good standing: International Discordance of Kilted Apiarists, Local #994. I'm Paraplegic Racehorse. http://www.paraplegicracehorse.net/ -- 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/BANLkTimDmUCCUbo=akb5ay1jbqb-rsm...@mail.gmail.com
Bug#625890: testing install report
Hi, more info on the issue: on syslog: ... May 6 18:36:51 main-menu[274]: INFO: Menu item 'bootstrap-base' selected May 6 18:37:09 debootstrap: dpkg: warning: parsing file '/var/lib/dpkg/status' near line 4 package 'dpkg': May 6 18:37:09 debootstrap: missing description May 6 18:37:09 debootstrap: dpkg: warning: parsing file '/var/lib/dpkg/status' near line 4 package 'dpkg': May 6 18:37:09 debootstrap: missing architecture May 6 18:37:09 debootstrap: dpkg: warning: 'sh' not found in PATH or not execut able. May 6 18:37:09 debootstrap: dpkg: warning: 'tar' not found in PATH or not execu table. May 6 18:37:09 debootstrap: dpkg: error: 2 expected programs not found in PATH or not executable. May 6 18:37:09 debootstrap: Note: root's PATH should usually contain /usr/local /sbin, /usr/sbin and /sbin. ... And the first part of /var/lib/dpkg/status, which may be relevant due to dpkg/status warning: Package: uinput-modules-2.6.37-2-486-di Status: install ok unpacked Version: 1.102 Provides: uinput-modules Depends: kernel-image-2.6.37-2-486-di Description: uinput support Package: libblkid1-udeb Status: install ok installed Version: 2.17.2-9.1 ... -- Melhores cumprimentos/Best regards, Miguel Figueiredo http://www.DebianPT.org -- 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/201105061947.43092.el...@debianpt.org
NOVATO EN DEBIAN
hola señore de debian me pueden enviar libros en española respecto a debian soy nobato en linux por fabor lo necesito, gracias de ante mano saludos atte.: ruben
Re: Preseeded d-i image doesn't boot from USB anymore
Hi Mario, On Fri, 6 May 2011 17:56:41 +0200, Mario Fux debian...@unormal.org wrote: To regenerate the debian ISO I use the attached script (modified from [1]) and here is a short extract of the included commands: Ah, I see, you're using the new clever Just copy it to the stick .ISO Those images are built with xorriso, rather than genisoimage, which is what makes it possible to boot from them like that (although others will need to tell you exactly how that's done, since I've not tried doing that yet). You may find that you'd be better off using the old USB method, which is to make a bootable USB stick with a FAT partition on it, and then put the ISO image in that partition as a file. The simple way of doing this is to unzip the boot.img.gz you can find via this link: http://www.debian.org/distrib/netinst#verysmall by selecting the architecture you need, then hd-media. If you want to vary the size of the filesystem on the stick, you'll need to recreate the file system, as described in the Flexible way section here: http://d-i.alioth.debian.org/manual/en.i386/ch04s03.html Either way, making a USB stick like this has the advantage that the preseed can then just be a file or set of files on the USB stick, which makes them editable. See mentions of USB on this page: http://d-i.alioth.debian.org/manual/en.i386/apbs02.html#preseed-auto If you want to do multi-file preseeding, with includes, you should note the stuff about magic URLs with /./ in them, here: http://hands.com/d-i/ So, if you want this fully automatic, I normally do that by adding an option to the advanced menu (see adtext.cfg in the VFAT filesystem on the USB stick you've created by this point) or the main menu (text.cfg) specifying the preseed file as an extra kernel parameter, something like: label myautoinstall menu label ^Dangerous Auto-Install, no questions asked kernel linux append vga=normal initrd=initrd.gz file=/hd-media/./preseed.cfg -- quiet where the clever bit is the file=/hd-media/./preseed.cfg which makes D-I look in the root of the USB stick for a file called preseed.cfg Once you've got that setup, you can tweak the preseed.cfg to your heart's content without needing to remaster CDs all the time (which gets tiresome _very_ quickly indeed). BTW I like to have a git repository on my USB sticks for tracking the changes to preseeds, since that allows you to easily push changes back to somewhere else, and then suck them down onto another stick later. HTH Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560]http://www.hands.com/ |-| HANDS.COM Ltd.http://www.uk.debian.org/ |(| 10 Onslow Gardens, South Woodford, London E18 1NE ENGLAND pgpsGn58f98sf.pgp Description: PGP signature
Bug#625890: testing install report
In attachment the logs until the error happened. -- Melhores cumprimentos/Best regards, Miguel Figueiredo http://www.DebianPT.org syslog.gz Description: GNU Zip compressed data status.gz Description: GNU Zip compressed data
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * FAILED BUILD: armel May 06 18:17 joey@box build_orion5x_network-console http://people.debian.org/~joeyh/d-i/armel/images/daily/build_orion5x_network-console.log * OLD BUILD:mips Apr 20 00:19 buildd@ball build_malta_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_malta_netboot-2.6.log * OLD BUILD:mips Apr 20 00:23 buildd@ball build_r4k-ip22_cdrom-2.6 http://d-i.debian.org/daily-images/mips/daily/build_r4k-ip22_cdrom-2.6.log * OLD BUILD:mips Apr 20 00:27 buildd@ball build_r4k-ip22_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_r4k-ip22_netboot-2.6.log * OLD BUILD:mips Apr 20 00:32 buildd@ball build_r5k-ip32_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_r5k-ip32_netboot-2.6.log * OLD BUILD:mips Apr 20 00:37 buildd@ball build_sb1-bcm91250a_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_sb1-bcm91250a_netboot-2.6.log * OLD BUILD:mips Apr 20 00:38 buildd@ball build_miniiso http://d-i.debian.org/daily-images/mips/daily/build_miniiso.log * OLD BUILD:s390 May 01 00:03 buildd@zandonai build_generic http://d-i.debian.org/daily-images/s390/daily/build_generic.log * OLD BUILD:s390 May 01 00:03 buildd@zandonai build_tape http://d-i.debian.org/daily-images/s390/daily/build_tape.log * FAILED BUILD: amd64 May 06 23:10 debian-cd@pettersson 1wheezymips http://cdbuilder.debian.org/cdimage-log/1wheezymips * FAILED BUILD: amd64 May 06 23:10 debian-cd@pettersson 1sidmips http://cdbuilder.debian.org/cdimage-log/1sidmips * FAILED BUILD: amd64 May 06 23:11 debian-cd@pettersson 2wheezymips http://cdbuilder.debian.org/cdimage-log/2wheezymips * FAILED BUILD: amd64 May 06 23:11 debian-cd@pettersson 2sidmips http://cdbuilder.debian.org/cdimage-log/2sidmips * FAILED BUILD: amd64 May 06 23:18 debian-cd@pettersson 1sidkfreebsd-amd64 http://cdbuilder.debian.org/cdimage-log/1sidkfreebsd-amd64 * FAILED BUILD: amd64 May 06 23:19 debian-cd@pettersson 2sidkfreebsd-amd64 http://cdbuilder.debian.org/cdimage-log/2sidkfreebsd-amd64 * FAILED BUILD: amd64 May 06 23:19 debian-cd@pettersson 1sidkfreebsd-i386 http://cdbuilder.debian.org/cdimage-log/1sidkfreebsd-i386 * FAILED BUILD: amd64 May 06 23:20 debian-cd@pettersson 2sidkfreebsd-i386 http://cdbuilder.debian.org/cdimage-log/2sidkfreebsd-i386 Totals: 109 builds (9 failed, 8 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/e1qivsj-yt...@ravel.debian.org
