Your message dated Sun, 25 Aug 2013 12:42:38 +0200 with message-id <201308251243.25305.holger@layer-acht.org> and subject line dealing with old installation-reports has caused the Debian Bug report #682507, regarding Can not detect a network card 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.) -- 682507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682507 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Can not detect a network card
- From: Reshetnikov Artyom <a_reshetnikov@lavabit.com>
- Date: Mon, 23 Jul 2012 15:56:02 +0400
- Message-id: <500D3BD2.8040400@lavabit.com>
Package: installation-reports Boot method: CDImage version: http://caesar.acc.umu.se/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.isoDate: July 20, 2012 Initial boot: [O] Detect network card: [E] Comments/Problems:At the step of detecting the network card, the installer clears all of the messages from screen and hangs. But it is possible to press Ctrl-Cand return to the main menu. Moreover, it is possible to continue, the installer sets up the network correctly. I was really confused by such behavior and thought that the installer really hangs. Also, I tried AMD64-image, both booting from CD and using setup.exe - causes the same error. Also, pressing Ctrl-Alt-Del or running /sbin/reboot hangs the current console, Alt-SysRq-K required.Attachment: install-report.tar
Description: Binary data
--- End Message ---
--- Begin Message ---
- To: 696737-done@bugs.debian.org, 607698-done@bugs.debian.org, 606496-done@bugs.debian.org, 603960-done@bugs.debian.org, 701827-done@bugs.debian.org, 686786-done@bugs.debian.org, 685681-done@bugs.debian.org, 685515-done@bugs.debian.org, 685047-done@bugs.debian.org, 685308-done@bugs.debian.org, 684639-done@bugs.debian.org, 683706-done@bugs.debian.org, 683705-done@bugs.debian.org, 683381-done@bugs.debian.org, 682753-done@bugs.debian.org, 682507-done@bugs.debian.org, 682008-done@bugs.debian.org, 680555-done@bugs.debian.org, 681673-done@bugs.debian.org, 680026-done@bugs.debian.org, 679795-done@bugs.debian.org, 675127-done@bugs.debian.org, 674855-done@bugs.debian.org, 672317-done@bugs.debian.org, 673649-done@bugs.debian.org, 605076-done@bugs.debian.org, 690752-done@bugs.debian.org, control@bugs.debian.org
- Subject: dealing with old installation-reports
- From: Holger Levsen <holger@layer-acht.org>
- Date: Sun, 25 Aug 2013 12:42:38 +0200
- Message-id: <201308251243.25305.holger@layer-acht.org>
reassign 701201 src:linux retitle 701201 libata.atapi_passthru16=0 is needed by some hardware forcemerge 690985 686954 thanks 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. 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 ---