Your message dated Sat, 31 Aug 2013 12:52:55 +0200 with message-id <201308311253.30231.holger@layer-acht.org> and subject line dealing with old installation-reports has caused the Debian Bug report #695180, regarding Installation report 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.) -- 695180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695180 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Installation report
- From: "The Pabster" <the.pabster@yahoo.com>
- Date: Wed, 05 Dec 2012 00:42:54 -0000
- Message-id: <op.wotixsnftuz2aj@triton>
Package: installation-reports
Boot method: Debian-testing-64-kde-iso "burned" to an USB
Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta4/amd64/iso-cd/debian-wheezy-DI-b4-amd64-kde-CD-1.iso
Date: 3-December-2012
Machine: Toshiba Portégé Z830
Processor: i5
Memory: 4Gb
Partitions: /dev/sda1 ext4 mounted on /
Output of lspci -knn (or lspci -nn):00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0104] (rev 09)
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09)
00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network Connection [8086:1503] (rev 04)
00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04)
00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 04)
00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4)
00:1c.2 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 [8086:1c14] (rev b4)
00:1c.4 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 [8086:1c18] (rev b4)
00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 04)
00:1f.0 ISA bridge [0601]: Intel Corporation HM65 Express Chipset Family LPC Controller [8086:1c49] (rev 04)
00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller [8086:1c03] (rev 04)
01:00.0 System peripheral [0880]: Ricoh Co Ltd Device [1180:e823] (rev 07)
02:00.0 Network controller [0280]: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01)
03:00.0 USB controller [0c03]: NEC Corporation uPD720200 USB 3.0 Host Controller [1033:0194] (rev 04)
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: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Install base system: [O]
Clock/timezone setup: [O]
User/password setup: [O]
Install tasks: [O]
Install boot loader: [E]
Overall install: [O]
Comments/Problems:
Everything went almost all right. Only one issue: on my first attempt, despite having set the right partition on the main disk, at the end of the partitioning and disk setting step, the installer tried to format my SD card instead; so, I had to remove it in order for the installer not to get confused.And one suggestion: just before installing the system and after the warning "if you chose to use a mirror the next step might take very long" (or something like that), there is a step called "select and install packages"; however, you're not offered any kind of "selection" prior to installation, which is somewhat misleading, as there's nothing to select then: the installer starts installing packages right away. I suggest this step should read only "install packages".
--- End Message ---
--- Begin Message ---
- To: 695669-done@bugs.debian.org, 695476-done@bugs.debian.org, 695180-done@bugs.debian.org, 695058-done@bugs.debian.org, 695008-done@bugs.debian.org, 694934-done@bugs.debian.org, 694803-done@bugs.debian.org, 694788-done@bugs.debian.org, 694777-done@bugs.debian.org, 694771-done@bugs.debian.org, 694722-done@bugs.debian.org, 694247-done@bugs.debian.org, 694062-done@bugs.debian.org, 693891-done@bugs.debian.org, 693756-done@bugs.debian.org, 693756-done@bugs.debian.org, 692731-done@bugs.debian.org, 692475-done@bugs.debian.org, 692437-done@bugs.debian.org, 689849-done@bugs.debian.org
- Subject: dealing with old installation-reports
- From: Holger Levsen <holger@layer-acht.org>
- Date: Sat, 31 Aug 2013 12:52:55 +0200
- Message-id: <201308311253.30231.holger@layer-acht.org>
Hi, thank you for submitting installation reports, 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 were caused by broken hardware and/or - they have been from a development phase where things were not stable and/or - they are quite old (and thus likely fixed today) and/or - moreinfo was asked and not given 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 ---