Your message dated Wed, 08 Sep 2010 03:57:32 +0000
with message-id <[email protected]>
and subject line Closing old installation report #495792
has caused the Debian Bug report #495792,
regarding cdrom: Disk partioner hangs at 52% when manual disk partion option
selected
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 [email protected]
immediately.)
--
495792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495792
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cdrom
Severity: grave
Justification: renders package unusable
I was trying to install a new lenny system over an existing old-stable system
The computer has two disk drives used for a Raid1 configuration
MD0 is a small boot partition
MD1 is a LVM with four partitions (/ /home /var /chroot)
I tried both lenny beta-2 disk and the weekly snapshot. (The beta-2 wouldn't
boot on my machine so I
went to the snapshot disk)
When I selected the manual partition option, the partitioner would hang at 52%
and not
present the partition map of the system. Pressing 'F4' showed a detail screen
that
had both the raid and LVM partitions recognized.
The Stable install disk worked fine.
(The following is pulled from the machine I am reporting from and not from the
machine which
reported the problem)
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: from install disk
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
Installer.
- indications in the installation report give the feeling that
the reported problem waslying in another software, unrelated to
D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful
The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet.
In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.
You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.
If some problems are found, please report them with a new bug sent
against installation-reports.
Many thanks for your understanding and your help improving Debian,
past and present.
--- End Message ---
