Bug#175290: FTBFS on s390
Package: s390-dasd Version: 0.0.3 Severity: important Hi, the package build fails due to some missing header files, probably caused by missing build dependencies. The same is true for s390-netdevice. See http://buildd.debian.org/fetch.php?pkg=s390-dasdver=0.0.3arch=s390stamp=1041636326file=logas=raw for details. Thanks, Gerhard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Screenshots from the woody installation
Do we have any screenshots from the woody installation? If not, could somebody prepare some and send them to me (or a link and I'll wget them). This is a forwarded request from Personal Computer World, a UK-based PC magazine (www.pcw.co.uk). Regards, Joey -- Life is a lot easier when you have someone to share it with. -- Sean Perry Please always Cc to me when replying to me on the lists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Screenshots from the woody installation
On Sat, Jan 04, 2003 at 09:49:20PM +0100, Martin Schulze wrote: Do we have any screenshots from the woody installation? If not, could somebody prepare some and send them to me (or a link and I'll wget them). This is a forwarded request from Personal Computer World, a UK-based PC magazine (www.pcw.co.uk). If currently no screenshots are available I can make someone with vmware or serial console. Bye Thorsten -- Thorsten Sauter [EMAIL PROTECTED] (Is there life after /sbin/halt -p?) msg25113/pgp0.pgp Description: PGP signature
Bug#172580: fixied in cvs
I had a play on merulo.debian.org and sorted it out, the fix has been commited to busybox cvs, will upload a new package in the next day or so. Glenn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
busybox-cvs_0.60.99.cvs20030105-1_i386.changes ACCEPTED
Accepted: busybox-cvs-static_0.60.99.cvs20030105-1_i386.deb to pool/main/b/busybox-cvs/busybox-cvs-static_0.60.99.cvs20030105-1_i386.deb busybox-cvs-udeb_0.60.99.cvs20030105-1_i386.udeb to pool/main/b/busybox-cvs/busybox-cvs-udeb_0.60.99.cvs20030105-1_i386.udeb busybox-cvs_0.60.99.cvs20030105-1.dsc to pool/main/b/busybox-cvs/busybox-cvs_0.60.99.cvs20030105-1.dsc busybox-cvs_0.60.99.cvs20030105-1.tar.gz to pool/main/b/busybox-cvs/busybox-cvs_0.60.99.cvs20030105-1.tar.gz busybox-cvs_0.60.99.cvs20030105-1_i386.deb to pool/main/b/busybox-cvs/busybox-cvs_0.60.99.cvs20030105-1_i386.deb Announcing to [EMAIL PROTECTED] Closing bugs: 172580 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#172580: marked as done (busybox-cvs_0.60.99.cvs20021210-1(unstable/ia64): FTBFS: redefinition of `struct sysinfo')
Your message dated Sat, 04 Jan 2003 21:47:12 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#172580: fixed in busybox-cvs 0.60.99.cvs20030105-1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 11 Dec 2002 01:01:52 + From [EMAIL PROTECTED] Tue Dec 10 19:01:51 2002 Return-path: [EMAIL PROTECTED] Received: from winfree.gag.com [192.133.104.8] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 18LvG3-Zb-00; Tue, 10 Dec 2002 19:01:51 -0600 Received: from spampd.localdomain (localhost [127.0.0.1]) by winfree.gag.com (Postfix) with ESMTP id 72080C13F for [EMAIL PROTECTED]; Tue, 10 Dec 2002 18:01:51 -0700 (MST) Received: from rover.gag.com (rover.gag.com [192.133.104.32]) by winfree.gag.com (Postfix) with ESMTP id 6D20CC13F for [EMAIL PROTECTED]; Tue, 10 Dec 2002 18:01:50 -0700 (MST) Received: by rover.gag.com (Postfix, from userid 1000) id 80A7143C24; Tue, 10 Dec 2002 18:01:14 -0700 (MST) To: [EMAIL PROTECTED] Subject: busybox-cvs_0.60.99.cvs20021210-1(unstable/ia64): FTBFS: redefinition of `struct sysinfo' From: Bdale Garbee [EMAIL PROTECTED] Date: Tue, 10 Dec 2002 18:01:14 -0700 Message-ID: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=0.6 required=5.0 tests=SPAM_PHRASE_00_01 version=2.41 X-Spam-Level: Package: busybox-cvs Version: 0.60.99.cvs20021210-1 Severity: important This package fails on the ia64 autobuilder as shown below. Bdale | Automatic build of busybox-cvs_0.60.99.cvs20021210-1 on caballero by sbuild/ia64 |1.169 | Build started at 20021210-2306 [...] | gcc -I./include -Wall -Wstrict-prototypes -Wshadow -Os -fomit-frame-pointer |-D_GNU_SOURCE -c -o networking/libiproute/ipaddress.o |networking/libiproute/ipaddress.c | In file included from include/busybox.h:43, | from networking/libiproute/ipaddress.c:37: | include/libbb.h:191: redefinition of `struct sysinfo' | make[1]: *** [networking/libiproute/ipaddress.o] Error 1 [...] A complete build log can be found at http://buildd.debian.org/build.php?arch=ia64pkg=busybox-cvsver=0.60.99.cvs20021210-1 --- Received: (at 172580-close) by bugs.debian.org; 5 Jan 2003 02:53:25 + From [EMAIL PROTECTED] Sat Jan 04 20:53:25 2003 Return-path: [EMAIL PROTECTED] Received: from auric.debian.org [206.246.226.45] (mail) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 18V0uj-0006Kb-00; Sat, 04 Jan 2003 20:53:25 -0600 Received: from katie by auric.debian.org with local (Exim 3.35 1 (Debian)) id 18V0oi-0002zu-00; Sat, 04 Jan 2003 21:47:12 -0500 From: Glenn McGrath [EMAIL PROTECTED] To: [EMAIL PROTECTED] X-Katie: $Revision: 1.29 $ Subject: Bug#172580: fixed in busybox-cvs 0.60.99.cvs20030105-1 Message-Id: [EMAIL PROTECTED] Sender: Archive Administrator [EMAIL PROTECTED] Date: Sat, 04 Jan 2003 21:47:12 -0500 Delivered-To: [EMAIL PROTECTED] We believe that the bug you reported is fixed in the latest version of busybox-cvs, which is due to be installed in the Debian FTP archive: busybox-cvs-static_0.60.99.cvs20030105-1_i386.deb to pool/main/b/busybox-cvs/busybox-cvs-static_0.60.99.cvs20030105-1_i386.deb busybox-cvs-udeb_0.60.99.cvs20030105-1_i386.udeb to pool/main/b/busybox-cvs/busybox-cvs-udeb_0.60.99.cvs20030105-1_i386.udeb busybox-cvs_0.60.99.cvs20030105-1.dsc to pool/main/b/busybox-cvs/busybox-cvs_0.60.99.cvs20030105-1.dsc busybox-cvs_0.60.99.cvs20030105-1.tar.gz to pool/main/b/busybox-cvs/busybox-cvs_0.60.99.cvs20030105-1.tar.gz busybox-cvs_0.60.99.cvs20030105-1_i386.deb to pool/main/b/busybox-cvs/busybox-cvs_0.60.99.cvs20030105-1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Glenn McGrath [EMAIL PROTECTED] (supplier of updated busybox-cvs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 5 Jan 2003 12:48:05 +1100 Source: busybox-cvs Binary:
Bug#175385: modconf: Menu selection keeps jumping to the beginning of the menu after exiting submenu
Package: modconf Version: 0.2.43 Severity: normal Downloaded and use woody 3.0r0 cd's. Everything is okay until is get to module selection. If I scroll down to say the net/tulip section, enter it, and load my module, when I am done and exit back to the previous menu, it starts all the way back at the top of the main menu. Just a pain sometimes, especially if you make a mistake! Just a wish list. -- System Information Debian Release: 3.0 Kernel Version: Linux server 2.4.18-grsec-1.9.4 #1 SMP Sat Dec 14 04:12:31 CST 2002 i686 unknown Versions of the packages modconf depends on: ii modutils 2.4.15-1 Linux module utilities. ii whiptail 0.50.17-9.6Displays user-friendly dialog boxes from she ii whiptail 0.50.17-9.6Displays user-friendly dialog boxes from she ^^^ (Provides virtual package whiptail-provider) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#140579: Report: tftpboot install successfull
I understand that. But just like we have a bunch of architectures, we have a bunch of netboot options. You generally don't have a lot of choices about what your hardware supports. Telling someone whose card doesn't support pxe to use pxe because it's better is no more sensible than telling an m68k user to use the i386 boot floppies because i386 is better. True enough. So why does that prevent us from giving an overview of the various options and providing some criteria to help users pick one or the other? It may be true that generally better or worse doesn't matter -- just anything that works will do. On installing Debian, it would be very difficult for users to get a ROM burning, however there would be a lot of eepro cards which can PXE boot. I would rather like to be able to netboot with grub floppies, so that it only requires one floppy (grub) to start up the installation, but that requires an extracted image of the installation disk to use as NFS root, and a kernel vmlinuz image available via TFTP. I don't think we provide either images per default, but it might be worth considering for an option in the future, if grub cannot load tftpboot images. For using GRUB to start install: set up server to allow TFTP, and provide vmlinuz, and allow nfs export. get grub source and recompile with network card support, and create a floppy using dd command. ./configure --enable-eepro100 make dd if=stage1/stage1 of=image dd if=stage2/stage2 of=image bs=512 seek=1 dd if=image of=/dev/fd0 ; sync Then start the machine with the floppy (the following example will work on many installations): grub ifconfig --address=192.168.1.2 --server=192.168.1.1 grub kernel (nd)/boot/vmlinuz init=/bin/sh root=/dev/nfs nfsroot=192.168.1.1:/,flags=ro init=/bin/sh grub boot The above example will load the kernel via eepro card from /boot/vmlinuz on 192.168.1.1, and use / of the 192.168.1.1 as the / of 192.168.1.2 (the one to be installed) read-only via NFS, using /bin/sh as initial program. It is trivial to start up dbootstrap in this way also. regards, junichi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
