Bug#728344: debootstrap does not report errors
Package: debootstrap Version: 1.0.55 Severity: normal Hello. I get debootstrap failure without any diagnostic message (full output): # debootstrap --foreign --arch=armhf --verbose wheezy . I: Retrieving Release I: Retrieving Release.gpg I: Checking Release signature I: Valid Release signature (key id ED6D65271AACF0FF15D123036FB2A1C265FFB764) I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... I: Found additional required dependencies: insserv libbz2-1.0 libdb5.1 libsemanage-common libsemanage1 libslang2 libustr-1.0-1 I: Found additional base dependencies: libept1.4.12 libgcrypt11 libgnutls26 libgpg-error0 libidn11 libnfnetlink0 libp11-kit0 libsqlite3-0 libtasn1-3 libxapian22 I: Checking component main on http://ftp.us.debian.org/debian... I: Validating libacl1 2.2.51-8 I: Validating adduser 3.113+nmu3 I: Validating apt 0.9.7.9 I: Validating apt-utils 0.9.7.9 I: Validating libapt-inst1.5 0.9.7.9 I: Validating libapt-pkg4.12 0.9.7.9 I: Validating aptitude 0.6.8.2-1 I: Validating aptitude-common 0.6.8.2-1 I: Validating libattr1 1%3a2.4.46-8 I: Validating base-files 7.1wheezy2 I: Validating base-passwd 3.5.26 I: Validating bash 4.2+dfsg-0.1 I: Validating libboost-iostreams1.49.0 1.49.0-3.2 I: Validating bsdmainutils 9.0.3 I: Validating libbz2-1.0 1.0.6-4 I: Validating coreutils 8.13-3.5 I: Validating cpio 2.11+dfsg-0.1 I: Validating cron 3.0pl1-124 I: Validating libcwidget3 0.5.16-3.4 I: Validating dash 0.5.7-3 I: Validating libdb5.1 5.1.29-5 I: Validating debconf 1.5.49 I: Validating debconf-i18n 1.5.49 I: Validating debian-archive-keyring 2012.4 I: Validating debianutils 4.3.2 I: Validating diffutils 1%3a3.2-6 I: Validating dpkg 1.16.12 I: Validating e2fslibs 1.42.5-1.1 I: Validating e2fsprogs 1.42.5-1.1 I: Validating libcomerr2 1.42.5-1.1 I: Validating libss2 1.42.5-1.1 I: Validating libc-bin 2.13-38 I: Validating libc6 2.13-38 I: Validating multiarch-support 2.13-38 I: Validating findutils 4.4.2-4 I: Validating gcc-4.7-base 4.7.2-5 I: Validating libgcc1 1%3a4.7.2-5 I: Validating libstdc++6 4.7.2-5 I: Validating libgdbm3 1.8.3-11 I: Validating gnupg 1.4.12-7+deb7u1 I: Validating gpgv 1.4.12-7+deb7u1 I: Validating libgnutls26 2.12.20-7 I: Validating grep 2.12-2 I: Validating groff-base 1.21-9 I: Validating gzip 1.5-1.1 I: Validating hostname 3.11 I: Validating ifupdown 0.7.8 I: Validating insserv 1.14.0-5 I: Validating iproute 20120521-3+b3 I: Validating iptables 1.4.14-3.1 I: Validating iputils-ping 3%3a20101006-1+b2 I: Validating isc-dhcp-client 4.2.2.dfsg.1-5+deb70u6 I: Validating isc-dhcp-common 4.2.2.dfsg.1-5+deb70u6 I: Validating kmod 9-3 I: Validating libkmod2 9-3 I: Validating libept1.4.12 1.0.9 I: Validating libgcrypt11 1.5.0-5+deb7u1 I: Validating libgpg-error0 1.10-3.1 I: Validating libidn11 1.25-2 I: Validating liblocale-gettext-perl 1.05-7+b3 I: Validating libnfnetlink0 1.0.0-1.1 I: Validating libpipeline1 1.2.1-1 I: Validating libselinux1 2.1.9-5 I: Validating libsemanage-common 2.1.6-6 I: Validating libsemanage1 2.1.6-6 I: Validating libsepol1 2.1.4-3 I: Validating libsigc++-2.0-0c2a 2.2.10-0.2 I: Validating libtasn1-3 2.13-2 I: Validating libtext-charwidth-perl 0.04-7+b2 I: Validating libtext-iconv-perl 1.7-5 I: Validating libtext-wrapi18n-perl 0.06-7 I: Validating libusb-0.1-4 2%3a0.1.12-20+nmu1 I: Validating logrotate 3.8.1-4 I: Validating lsb-base 4.1+Debian8+deb7u1 I: Validating man-db 2.6.2-1 I: Validating manpages 3.44-1 I: Validating mawk 1.3.3-17 I: Validating nano 2.2.6-1+b2 I: Validating libncurses5 5.9-10 I: Validating libncursesw5 5.9-10 I: Validating libtinfo5 5.9-10 I: Validating ncurses-base 5.9-10 I: Validating ncurses-bin 5.9-10 I: Validating net-tools 1.60-24.2 I: Validating netbase 5.0 I: Validating netcat-traditional 1.10-40 I: Validating libnewt0.52 0.52.14-11.1 I: Validating whiptail 0.52.14-11.1 I: Validating libssl1.0.0 1.0.1e-2 I: Validating libp11-kit0 0.12-3 I: Validating libpam-modules 1.1.3-7.1 I: Validating libpam-modules-bin 1.1.3-7.1 I: Validating libpam-runtime 1.1.3-7.1 I: Validating libpam0g 1.1.3-7.1 I: Validating perl-base 5.14.2-21+deb7u1 I: Validating libpopt0 1.16-7 I: Validating libprocps0 1%3a3.3.3-3 I: Validating procps 1%3a3.3.3-3 I: Validating libreadline6 6.2+dfsg-0.1 I: Validating readline-common 6.2+dfsg-0.1 I: Validating rsyslog 5.8.11-3 I: Validating sed 4.2.1-10 I: Validating sensible-utils 0.0.7 I: Validating login 1%3a4.1.5.1-1 I: Validating passwd 1%3a4.1.5.1-1 I: Validating libslang2 2.2.4-15 I: Validating libsqlite3-0 3.7.13-1+deb7u1 I: Validating initscripts 2.88dsf-41+deb7u1 I: Validating sysv-rc 2.88dsf-41+deb7u1 I: Validating sysvinit 2.88dsf-41+deb7u1 I: Validating sysvinit-utils 2.88dsf-41+deb7u1 I: Validating tar 1.26+dfsg-0.1 I: Validating tasksel 3.14.1 I: Validating tasksel-data 3.14.1 I: Validating info 4.13a.dfsg.1-10 I: Validating install-info 4.13a.dfsg.1-10 I: Validating traceroute 1%3a2.0.18-3 I: Validating tzdata
Bug#721627: debian-installer: cannot install bootloader when multiple disks are present
Package: debian-installer Severity: important Hello, I am installing Debian Wheezy from a mini iso on an USB thumb drive (sda) to internal SATA harddisk (sdd). sdb and sdc are possibly non-existent floppies or something. When I get to installing grub the installer insists on installing to sda which - is bogus because I need the bootloader on sdd which has the system on it - fails because sda does not have a PC partition table Please make Debian installeble from USB thumb drive. Thanks -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (500, 'testing'), (410, 'unstable'), (200, 'experimental'), (150, 'precise-updates'), (150, 'precise-security'), (150, 'precise') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20130902143412.18695.53401.report...@optiplex960.ruk.cuni.cz
Bug#712675: debian-installer: fails to install in-place using network installer hybrid iso booted from local harddisk
Package: debian-installer Severity: normal Hello, I tried installing on a machine with BIOS problems that only boots from local disk or network. I did not have network installer ready but had another live system on the local harddisk so I wrote the netinst iso hybrid image over it. I noticed a few issues installing from the harddisk: - the installer fails to locate the iso on the disk. The disk has to be manually selected to load installer modules - the iso is not unmounted prior to partitioning so partitioning step fails - the partitioning step does not wipe the disk enough so when grub instalation is attempted on the disk it refuses to install because it thinks the disk has an ISO filesystem and is a CD-ROM with readonly 2k sectors Thanks Michal -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (910, 'testing'), (900, 'stable'), (610, 'oldstable'), (410, 'unstable'), (200, 'experimental'), (150, 'precise-updates'), (150, 'precise-security'), (150, 'precise') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20130618135009.12531.40225.report...@optiplex960.ruk.cuni.cz
Bug#697488: debootstrap: wrong default mirror
Package: debootstrap Version: 1.0.44 Severity: normal Hello, I tried to bootstrap a chroot and in the chroot that sources.list is pre-filled with the US mirror. Since the recommended mirrror is http://http.debian.net the default should perhaps reflect this. Thanks -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (910, 'testing'), (900, 'stable'), (410, 'unstable'), (200, 'experimental'), (150, 'precise-updates'), (150, 'precise-security'), (150, 'precise') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages debootstrap depends on: ii wget 1.13.4-3 Versions of packages debootstrap recommends: ii debian-archive-keyring 2012.4 ii gnupg 1.4.12-6 debootstrap suggests no packages. -- no debconf information -- 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/20130106015945.15661.55075.report...@optiplex960.ruk.cuni.cz
Bug#580340: debian-installer: Lenny fails to install on system with USB and SATA disks
Package: debian-installer Severity: normal I installed Debian Lenny on a system with a SATA hardrive and a built-in USB card reader. As the card reader driver is loaded before the SATA drivers during installation and after SATA driver during boot the instaleed system fails to boot searching for root in one of the card reader slots. -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20100505113046.28966.29610.report...@test2.ruk.cuni.cz
Bug#576206: debian-installer: [ppc] does not work with serial console
Package: debian-installer Severity: normal qemu-system-ppc -m 1024 -net nic -net tap,ifname=tap0,script=no,downscript=nomg -cdrom debian-504-powerpc-netinst.iso -boot d -nographic does not seem to do anything. Without -nographic a prompt on yellow screen appears where you can type something to boot an installer. -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (900, 'stable'), (700, 'testing'), (500, 'unstable'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34-rc1-atom64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20100401150449.12524.71052.report...@ipx7a-ion.ruk.cuni.cz
Bug#576206: debian-installer: [ppc] does not work with serial console
On 04/01/2010 05:03 PM, Frans Pop wrote: tag 576206 moreinfo thanks On Thursday 01 April 2010, Michal Suchanekhramr...@centrum.cz wrote: qemu-system-ppc -m 1024 -net nic -net tap,ifname=tap0,script=no,downscript=nomg -cdrom debian-504-powerpc-netinst.iso -boot d -nographic Sorry, part of the commandline got lost somehow: qemu-system-ppc -m 1024 -net nic -net tap,ifname=tap0,script=no,downscript=no ppc.img -cdrom debian-504-powerpc-netinst.iso -boot d -nographic does not seem to do anything. Without -nographic a prompt on yellow screen appears where you can type something to boot an installer. I think this is an error in how you're trying to boot the installer or your qemu invocation rather than a bug. I don't really know anything about powerpc myself, nor how to use qemu for powerpc, so I suggest you ask on the debian-powerpc list for help. Changing the -boot d to -boot c gives access to the installed system with full serial support from the quik bootloader so I don't think this is the case. The installer does have serial console support and I'm not aware of any issues with that on real powerpc hardware. Perhaps on hardware different from the one qemu emulates? Thanks Michal -- 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/4bb4c5ee.9000...@ruk.cuni.cz
Bug#576206: debian-installer: [ppc] does not work with serial console
On 04/01/2010 06:03 PM, Frans Pop wrote: On Thursday 01 April 2010, Michal Suchanek wrote: Changing the -boot d to -boot c gives access to the installed system with full serial support from the quik bootloader so I don't think this is the case. Can you provide the boot log for the installer somehow? I can provide a boot log of the installed system or that of an installer running with graphics or the installation report with graphics (I think the installer saves some such thing somewhere). I cannot run the installer without graphics. It could be that the installer is actually running but does not print anything on the serial port but I doubt that is the case because with graphics I have to type the name of the image to boot. Thanks Michal -- 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/4bb4d5f4.8060...@ruk.cuni.cz
Bug#575914: debian-installer: cannot resize partitions after guided partitioning step
Package: debian-installer Version: 5.03 Severity: normal After the guided partitioning step the installer presents a screen where the partitions can be reviewed. However, the option to resize a partition is missing from the partition options menu. Partitions have to be deleted and re-created to resize them. -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (900, 'stable'), (700, 'testing'), (500, 'unstable'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34-rc1-atom64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20100330132548.1983.54378.report...@ipx7a-ion.ruk.cuni.cz
Bug#569057: console-setup: starting console-setup fails silently
Package: console-setup Version: 1.51 Severity: normal When starting console-setup from X the console is not configured but no error is printed. -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (900, 'stable'), (700, 'testing'), (500, 'unstable'), (110, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.33-rc6 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages console-setup depends on: ii console-terminus 4.26-2.1 Fixed-width fonts for fast reading ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii keyboard-configuration1.51 system-wide keyboard preferences ii xkb-data 1.7-2 X Keyboard Extension (XKB) configu Versions of packages console-setup recommends: ii console-tools 1:0.2.3dbs-68 Linux console and font utilities ii kbd-compat [kbd] 1:0.2.3dbs-68 Wrappers around console-tools for Versions of packages console-setup suggests: ii locales 2.10.2-5 Embedded GNU C Library: National L ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip -- debconf information excluded -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Mad idea: grub-fuse
2009/9/7 Colin Watson cjwat...@ubuntu.com: On Mon, Sep 07, 2009 at 06:39:13PM +0800, Bean wrote: On Mon, Sep 7, 2009 at 6:18 PM, Colin Watsoncjwat...@ubuntu.com wrote: The level of functionality provided by the existing filesystem modules would be quite sufficient. Oh I see, you mean the other way around, using the grub fs code to implement a FUSE driver. But I don't see why not just modify os-prober to work with grub-fstest, this is much simpler than writing a FUSE wrapper. The changes to do that in os-prober would be sufficiently intrusive that they simply aren't going to happen (remember that os-prober needs to work without GRUB too). A FUSE wrapper would make it possible to just replace the mount step, which is much easier from the client side. (Yes, I know it's some work in GRUB, which is why this thread is labelled Mad idea.) This is actually quite useful. The support for BSD filesystems on Linux is quite poor, and it's the same the other way around but both implement FUSE. With FUSE grub can find kernels on any filesystems from which it can load them regardless of the limitations of the system on which os-prober runs. Thanks Michal -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Mad idea: grub-fuse
2009/9/7 Vladimir 'phcoder' Serbinenko phco...@gmail.com: On Mon, Sep 7, 2009 at 11:30 AM, Colin Watsoncjwat...@ubuntu.com wrote: os-prober mounts filesystems using Linux's filesystem drivers. This of course means that we have to go to special lengths to avoid replaying journals (we don't yet, but we should), we have to load huge piles of filesystem modules, etc. Today's crazy idea was to implement a FUSE wrapper for grub-fstest, thereby providing a read-only filesystem mount using GRUB's filesystem drivers. There would be lots of things you probably wouldn't be able to do this way, but it would be enough to support os-prober (which could of course only use this optionally, but even so). I can't decide whether or not this is a terrible idea, so I'm sending mail in case somebody thinks it's a good idea and wants to run with it. :-) Actually I had this idea before but haven't had any time to implement or think more about it. This would be useful for massive multi-OS environment since fuse is available on many platforms but many of FS drivers aren't. Implementing fuse wrapper for grub fs drivers is useful. However I'm not sure if it should go to main repository - this project isn't really about booting. I think that it's useful but should be a separate spin-off project Since we want grub use this module and at this point in time the FUSE interface is more stable than grub interfaces I think it would be more natural to start developing this kind of module with GRUB unless there are some license issues. After all, grub includes other tools that are meant for running outside of GRUB. The question remains who (if anybody at all) writes the wrapper. Thanks Michal -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [Fwd: Upcoming Lenny Point Release]
2009/6/5 Luk Claes l...@debian.org: Hi Forwarding this announcement as it might directly affect your team. Don't hesitate to forward it further if you think that can be useful. Cheers Luk Is it feasible to get httpfs into Debian still? I intended to look at it some time in the near future. AFAIK tehre are two unresolved problems - it lacks a man page - it can be stopped by typing ^Z on the console while d-l is booting (or at least you could in the past) Another issu is I am not a DD. Thanks Michal -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Help testing syslinux
On 09/09/2008, Michal Suchanek [EMAIL PROTECTED] wrote: On 09/09/2008, Chris Lamb [EMAIL PROTECTED] wrote: Michal Suchanek wrote: However, the syslinux on the broken CD is also version 3.71. I wonder what's going on here. You will have to be more precise; there are both broken and fixed.versions of syslinux with that version prefix. The syslinux on the 50M test ISOs is 2:3.71+dfsg-3, which is already in testing. I will try to rebuild once more to be sure but it looks like the syslinux I have installed is also dfsg-3. I must have built the image just before a round of updates. It took quite a few modifications to rebuild, and the new image now works. Thanks Michal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Help testing syslinux
On 03/09/2008, Daniel Baumann [EMAIL PROTECTED] wrote: Hi, upstream has fixed the qemu bug in syslinux (yay!), updated syslinux version has been uploaded to sid already. Hello, The syslinux currently in Lenny does not work for me ( after displaying or press Enter to the screen shows bw random looking pattern). However, the testing image boots. Using some Sempron+VIA (K8M800?) system. Thanks Michal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Help testing syslinux
On 09/09/2008, Michal Suchanek [EMAIL PROTECTED] wrote: On 03/09/2008, Daniel Baumann [EMAIL PROTECTED] wrote: Hi, upstream has fixed the qemu bug in syslinux (yay!), updated syslinux version has been uploaded to sid already. Hello, The syslinux currently in Lenny does not work for me ( after displaying or press Enter to the screen shows bw random looking pattern). However, the testing image boots. Using some Sempron+VIA (K8M800?) system. However, the syslinux on the broken CD is also version 3.71. I wonder what's going on here. Thanks Michal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Help testing syslinux
On 09/09/2008, Chris Lamb [EMAIL PROTECTED] wrote: Michal Suchanek wrote: However, the syslinux on the broken CD is also version 3.71. I wonder what's going on here. You will have to be more precise; there are both broken and fixed.versions of syslinux with that version prefix. The syslinux on the 50M test ISOs is 2:3.71+dfsg-3, which is already in testing. I will try to rebuild once more to be sure but it looks like the syslinux I have installed is also dfsg-3. Thanks Michal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Help testing syslinux
On 03/09/2008, Daniel Baumann [EMAIL PROTECTED] wrote: Hi, upstream has fixed the qemu bug in syslinux (yay!), updated syslinux version has been uploaded to sid already. however, syslinux 3.71 does still have some regressions, therefore i've uploaded to small (50mb) test images for i386 and amd64: http://live.debian.net/syslinux-test/ It would be nice if a lot of people could test it and report any left regressions, together with the name of their computer model (or mainboard, if it's whitebox) and the bios vendor/version. It does not work on Intel iMacs because the keyboard emulation is broken there and you have to press a key to boot. It never worked, though. Thanks Michal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484799: busybox: mount -f should not mount
Package: busybox Version: 1:1.9.2-3 Severity: normal The whole point of mount -f is to write to /etc/mtab I guess, at least it's how it is sometimes used when the filesystem is mounted by other means. As I read the code mount in busybox sets some flag when mtab is used but ignores the flag when mtab is not used. It should just (or check that the mount *could* be done if it wants to do something - like that the files/directories exist). Attached patch should make bysybox exit when mount -f is used and mtab is not compiled in. Thanks -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23.3-src (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages busybox depends on: ii libc6 2.7-10 GNU C Library: Shared libraries busybox recommends no packages. -- no debconf information --- util-linux/mount.c~ 2008-02-12 17:03:13.0 +0100 +++ util-linux/mount.c 2008-06-06 13:57:23.0 +0200 @@ -1635,22 +1635,22 @@ // Parse remaining options opt = getopt32(argv, o:t:rwanfvsi, opt_o, fstype); + argv += optind; + argc -= optind; + + // Three or more non-option arguments? Die with a usage message. + if (argc 2) bb_show_usage(); + if (opt 0x1) append_mount_options(cmdopts, opt_o); // -o //if (opt 0x2) // -t if (opt 0x4) append_mount_options(cmdopts, ro); // -r if (opt 0x8) append_mount_options(cmdopts, rw); // -w //if (opt 0x10) // -a if (opt 0x20) USE_FEATURE_MTAB_SUPPORT(useMtab = 0); // -n - if (opt 0x40) USE_FEATURE_MTAB_SUPPORT(fakeIt = 1); // -f + if (opt 0x40) USE_FEATURE_MTAB_SUPPORT(fakeIt = 1)SKIP_FEATURE_MTAB_SUPPORT(exit(0)); // -f //if (opt 0x80) // -v: verbose (ignore) //if (opt 0x100) // -s: sloppy (ignore) //if (opt 0x200) // -i: don't call mount.fstype (ignore) - argv += optind; - argc -= optind; - - // Three or more non-option arguments? Die with a usage message. - - if (argc 2) bb_show_usage(); // If we have no arguments, show currently mounted filesystems
Bug#411552: debian-installer: USB keyboard support
Package: debian-installer Version: 40r2 Followup-For: Bug #411552 There are many (older) PC BIOSes that do support USB keyboard but only in BIOS, not once an OS (like syslinux) is booted. Of course, Linux can use the keyboard with appropriate drivers but syslinux cannot. This applies to recent Apple hardware as well. The PC BIOS emulation is quite flaky and the USB keyboard usually fails. It is said it can be restored with unplugging and replugging the keyboard, at least sometimes. There are workarounds for both cases. You can use the PS2 port if you have such keyboard around and nothing else is faulty. With Apple hardware Linux could supposedly boot natively using the efi thingy (although that might cause problems with graphics and stuff because most hardware is unitialized or initialized in a different way then). Thanks Michal -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23.3-src (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#477354: debian-installer: fails to bootstrap because of missing gpgv
Package: debian-installer Version: 40r2 Severity: important I tried to install debian with this installer CD: debian-40r2-i386-businesscard.iso 03-Jan-2008 01:4332M The GUI installer works but the default one fails bootstrap and complains that there is missing gpgv which is needed to verify packages. Thanks Michal -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23.3-src (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#477354: debian-installer: fails to bootstrap because of missing gpgv
On Apr 22, 2008, at 7:03 PM, Frans Pop wrote: Op 22-04-2008 om 17:41 schreef Michal Suchanek: The GUI installer works but the default one fails bootstrap and complains that there is missing gpgv which is needed to verify packages. I doubt that this is really a bug in the installer because otherwise we'd have had a lot more reports. Can you reproduce the error if you try again, preferably using a different mirror? If you can reproduce it, please send us the syslog for the installation (gzipped!). Yes, on a second try it worked so it must have been a mirror outage. I was not aware the package is downlodaded from the mirror - logically it should not be if it is used to validate the downloaded packages. Thanks MS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#417407: installing to a box with suspended system
Hello, I tried to use the installer on a box which had a Linux system suspended on one disk. As I noticed that os-prober mounts the partitions I did not try to resume. According to the software suspend documentation this could cause serious data loss, especially since the filesystem loses consistency while *mounted*. Thanks Michal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#417407: installing to a box with suspended system
On 31/10/2007, Frans Pop [EMAIL PROTECTED] wrote: On Wednesday 31 October 2007, Michal Suchanek wrote: I tried to use the installer on a box which had a Linux system suspended on one disk. As I noticed that os-prober mounts the partitions I did not try to resume. According to the software suspend documentation this could cause serious data loss, especially since the filesystem loses consistency while *mounted*. The installer will also in principle automatically reuse an existing swap partition during the installation... In my opinion this is a completely different issue than the subject of this report. I also think that trying to do an installation on a system that has an OS in suspended state is not very smart. _Any_ installation of an OS is inherently risky as you can never be sure exactly what changes it may make on disk. Compounding that risk by having operating systems suspended is something you should know to avoid as a user. We could add a warning about that in the installation guide, but I don't think there is much more that we can do than that. I would personally qualify any data loss resulting from that as being caused by user error. Setting follow-up for this to the mailing list as this does not belong in this bug report. Well, this is another problem that might be solved by the solution suggested for that bug. To paraphrase what you are saying, using Debian software on a system is inherently risky, as you can never be sure what changes it does. Compounding the risk by having operating systems suspended is something you should avoid as a user. Here the installer is no different from any other piece of software. It should not do stuff behind your back. It is not one of those tools for certain other OSes. The installer should be designed to perform the task of copying Debian to a place designated by the user in the system so that the user can boot Debian using the method she chooses. Modifying other places in the system is not part of this task. Thanks Michal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435891: cannot select timezone during installation
Package: installation Severity: important Tags: l10n I tried installing with the new graphical installer. Just downloaded from the 'current' directory on a mirror. In the timezone selection I cannot select my timezone because it is not offered. Only US timezones are displayed in the dialog (probably because I selected US English as the installer language). I do not want to decipher local gibberish while installing Debian and still want to use proper local timezone. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435893: debian-installer: the graphic installer is too bright
Package: debian-installer Severity: minor The new graphic installer is cool. However, I find the white background too bright to be comfortable. Compared to the text installer this is certainly a regression :) -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#408286: ignores errors during installation of arcboot
Package: arcboot-installer I tried installing Debian on a SGI O2. The mirror I selected did not have the arcboot and bvhtool packages for some reason. I could see errors in the fourth VT but the installer happily finished as if nothing happened. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
