Your message dated Sat, 20 Jul 2013 12:44:51 +0200 with message-id <201307201245.07701.holger@layer-acht.org> and subject line dealing with old debian-installer bugs has caused the Debian Bug report #511896, regarding debian-installer: Hanged at the partitioning step when installing on a partition previously created (with cfdisk) 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 owner@bugs.debian.org immediately.) -- 511896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511896 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: debian-installer: Hanged at the partitioning step when installing on a partition previously created (with cfdisk)
- From: Federico Pinal Moreira <federicopinal@yahoo.es>
- Date: Thu, 15 Jan 2009 15:20:31 +0100
- Message-id: <20090115142031.2481.87117.reportbug@debian>
Package: debian-installer Version: lenny rc1 Severity: important I have a virtualbox virtual machine with a 2.00GB disk (2GiB, actually) in which I have failed to install lenny using http://cdimage.debian.org/cdimage/lenny_di_rc1/i386/iso-cd/debian-testing-i386-netinst.iso because I get the error screen that I attach when I assign the mount points to the previously existant partitions. The disk was partitioned with cfdisk using the sequence of commands "logical partition - size 200 - at the end - another logical - size 1000 - at the end" so that I got this partition table: # fdisk -lu Disk /dev/hda: 2147 MB, 2147483648 bytes 16 heads, 63 sectors/track, 4161 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/hda1 1849680 4194287 1172304 5 Extended /dev/hda5 1849743 3803183 976720+ 83 Linux /dev/hda6 3803247 4194287 195520+ 82 Linux swap / Solaris When performing an expert install, in the "Partition disks" step, I selected "Partitioning method: Manual", / at partition #5, swap at partition #6. After the confirmation question my partitions had changed to: Disk /dev/hda: 2147 MB, 2147483648 bytes 16 heads, 63 sectors/track, 4161 cylinders, total 4194304 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00021bbf Device Boot Start End Blocks Id System /dev/hda1 1849742 4194287 1172273 5 Extended /dev/hda5 1849743 3803183 976720+ 83 Linux /dev/hda6 3803247 4194287 195520+ 82 Linux swap / Solaris If I try to reinstall with this new partition table the error happens again. This might be an example of the #440446 bugAttachment: error-message.png
Description: PNG imageAttachment: var-log-partman.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
- To: control@bugs.debian.org, 709436-done@bugs.debian.org, 246498-done@bugs.debian.org, 561870-done@bugs.debian.org, 591923-done@bugs.debian.org, 590771-done@bugs.debian.org, 598765-done@bugs.debian.org, 511896-done@bugs.debian.org, 509238-done@bugs.debian.org
- Subject: dealing with old debian-installer bugs
- From: Holger Levsen <holger@layer-acht.org>
- Date: Sat, 20 Jul 2013 12:44:51 +0200
- Message-id: <201307201245.07701.holger@layer-acht.org>
reassign 473144 win32-loader reassign 598653 discover reassign 511896 partman-base 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 - thats often better, as the bug log will be clearer and shorter and not contain cruft. cheers, HolgerAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---