Your message dated Sun, 21 Jul 2013 15:53:10 +0200 with message-id <201307211553.37517.hol...@layer-acht.org> and subject line dealing with old debian-installer bugs has caused the Debian Bug report #528043, regarding [debian-installer] mkfs hangs when formatting a major block device 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.) -- 528043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: debian-installer Severity: normal --- Please enter the report below this line. --- Hi, I tried to install lenny with the official net-install cd on i386 in a qemu environment. I did not partition /dev/hda, but choose to use the whole device for the root filesystem. This caused the "mkfs.ext3 /dev/hda" command to hang indefinitely. The reason seems to be the confirmation prompt of mkfs when trying to format a non-partition. Sending "y" via echo to stdin of the mkfs.ext3 process fixed the problem and allowed mkfs to progress as expected. I guess, the installer should add the "-F" switch for mkfs.ext3 in case of a non-partition target device. Obviously it is not recommended to use a whole block device for a filesystem. But since the installer seems to allow this, it should not hang later. thanks for your time, Lars -- gpg key: https://systemausfall.org/schluessel/lars-devel.0.ascsignature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---tags 697985 + moreinfo tags 647406 + wontifx thanks Hi, thank you for submitting bug reports concering debian-installer, much appreciated. I read through all the bugs mentioned here (and I'm sure they were read by several people at the time they were submitted) and am closing them now as/if - they (finally) indicated success and/or - I know from first hand experience that the functionality is working in Wheezy and/or - they only contained very little information and/or - they contained user errors and/or - they have been from a development phase where things were not stable and/or - they are very old and/or - they are wishlist but rather special + exotic and not have been acted on for years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to close wishlist bugs.) If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll do if requested) or just file a new one - and that's often better, as the bug log will be clearer and shorter and not contain cruft. cheers, Holgersignature.asc
Description: This is a digitally signed message part.
--- End Message ---