Your message dated Sat, 24 Aug 2013 17:57:31 +0200 with message-id <firstname.lastname@example.org> and subject line dealing with old installation-reports has caused the Debian Bug report #637873, regarding Failed kernel install does not allow re-select of kernel, Presented kernel options do not match installable options 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@example.com immediately.) -- 637873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637873 Debian Bug Tracking System Contact firstname.lastname@example.org with problems
--- Begin Message ---
- To: email@example.com
- Subject: Failed kernel install does not allow re-select of kernel, Presented kernel options do not match installable options
- From: Don Lachlan <firstname.lastname@example.org>
- Date: Sun, 14 Aug 2011 22:19:59 -0400
- Message-id: <20110815021957.GC9405@starscape.homelinux.net>Package: installation-reports Boot method: Virtual CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/20110814-1/i386/iso-cd/debian-testing-i386-businesscard.iso Date: 20110811.1800 EDT Machine: VirtualBox (Ubuntu 10.04) Processor: Intel Pentium M processor 1.60GHz Memory: 128M 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: [E] Clock/timezone setup: [O] User/password setup: [O] Install tasks: [ ] Install boot loader: [ ] Overall install: [E] Comments/Problems: Two issues: 1) Failed kernel install does not allow re-select of kernel: I tried to install linux kernel 2.6-686 and it accepted that choice, then errorer while installing the base system; it said 686 required PAE and my CPU didn't support it, I needed to go back and install the 486 version. However, after the base install failed, I could not change the kernel that I selected. I went back to the partition menu and formatted the disk again, then went to install the base system and it did not ask me what kernel I wanted, but again tried to install 2.6-686. Expected behavior: when a user selects "install base system", it should prompt to select a kernel image even if it has already been done. 2) Presented kernel options do not match installable options: I rebooted and started over and tried to install linux kernel 2.6-486; it instead installed linux kernel 3.0-486. It appeared that when I tried to install 2.6-686 that it was also installing 3.0. If 2.6 is no longer an option for wheezy, it should not be presented as an option. Also, the only linux kernel 3.0 that was listed was 3.0-486, even though 3.0-686 is installable by selecting the 2.6-686 kernel (and linux-image-686, I expect). Expected behavior: drop the options for 2.6, add 3.0-686.
--- End Message ---
--- Begin Message ---
- To: email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
- Subject: dealing with old installation-reports
- From: Holger Levsen <email@example.com>
- Date: Sat, 24 Aug 2013 17:57:31 +0200
- Message-id: <firstname.lastname@example.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). 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, Holger
Description: This is a digitally signed message part.
--- End Message ---