Your message dated Wed, 17 Jul 2013 11:38:31 +0200 with message-id <201307171139.02755.holger@layer-acht.org> and subject line dealing with old partman related bugs has caused the Debian Bug report #699136, regarding installation-reports: partman hangs on Dell Optiplex 960 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.) -- 699136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699136 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: installation-reports: partman hangs on Dell Optiplex 960
- From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
- Date: Sun, 27 Jan 2013 19:40:19 +0000
- Message-id: <20130127194019.2187.6962.reportbug@thesavage>
Package: installation-reports Severity: normal -- Package-specific info: Boot method: network Image version: wheezy non-graphical netboot from 2013-01-13 (i think) Date: <Date and time of the install> Machine: Dell Optiplex 960 Partitions: <df -Tl will do; the raw partition table is preferred> Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card: [O] Configure network: [O] Detect CD: [ ] Load installer modules: [O] Clock/timezone setup: [O] User/password setup: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system: [ ] Install tasks: [ ] Install boot loader: [ ] Overall install: [ ] Comments/Problems: partman hung at either 50% or 54% during the "Partition hard drives" phase of the installer. switching to a vt, i was able to see that it appeared to be hung during 35dump. killing parted from a vt was successful, but each time i tried to re-run partman, it hung on 35dump again. I ultimately installed manually, thanks to parted-deb and debootstrap :( --dkg -- I'm attaching the output of lshw -- i'm not sure what else would be useful. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
- To: control@bugs.debian.org, 587503-done@bugs.debian.org, 593998-done@bugs.debian.org, 684309-done@bugs.debian.org, 699136-done@bugs.debian.org, 692941-done@bugs.debian.org, 688869-done@bugs.debian.org, 684097-done@bugs.debian.org, 637784-done@bugs.debian.org, 598394-done@bugs.debian.org, 593545-done@bugs.debian.org, 593054-done@bugs.debian.org, 584297-done@bugs.debian.org, 563678-done@bugs.debian.org, 553482-done@bugs.debian.org, 547895-done@bugs.debian.org, 514643-done@bugs.debian.org, 511842-done@bugs.debian.org, 539522-done@bugs.debian.org
- Subject: dealing with old partman related bugs
- From: Holger Levsen <holger@layer-acht.org>
- Date: Wed, 17 Jul 2013 11:38:31 +0200
- Message-id: <201307171139.02755.holger@layer-acht.org>
reassign 693107 partman-auto reassign 670702 partman-auto reassign 615074 lvm2 reassign 676172 partman severity 691046 wishlist retitle 644430 document the need for a bios boot partition when using GPT forcemerge 644430 691046 reassign 691046 release-notes reassign 683747 partman-lvm reassign 671879 partman-base thanks Hi, thank you for submitting installation reports, much appreciated. I read through all the ("partman" related) bugs mentioned here and am closing them now as - 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 were (very) old. If I've closed a bug incorrectly please do reply or just file a new one - thats often better, as the bug log will be more clear. cheers, HolgerAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---