Re: missing lspci on a fresh install
On Mon, Sep 18, 2006 at 11:56:30PM +0200, Geert Stappers wrote: On Mon, Sep 18, 2006 at 11:24:17PM +0200, De Leeuw Guy wrote: Another question : where I post this kind of report ? If debian-boot is not the good place, ok, sorry for the disturb, but where ? I assume that the pointer to package 'base' has been seen. base is what the computer does need to boot. The computer can start without the lspci program, but it can't without a shell nor other essential programms. In other words: Install the package pciutils if you want the lspci tool Guy HtH GSt Hi, I want to say that Rick Thomas is my hero, he filed BR #388159 Rick Thomas is my hero, he filed bugreport #388159 Cheers Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#388159: missing lspci on a fresh install
reassign 388159 installation-reports retitle 388159 installation-reports: Please depend on lspci severity wishlist thanks Rick Thomas wrote: Package: base Please do not file bugs against the base pseudo-package. It is there just as a catch-all-I-dunno-where-to-file-this-report for users that can't really tell what package is giving them problems. All the bug reports here get reassigned to the right package. On Monday 18 September 2006 21:49, Rick Thomas wrote: On Sep 18, 2006, at 10:17 AM, De Leeuw Guy wrote: Frans Pop a écrit : The d-i team is not responsible for what is part of the base system and what is not. Then who is? Where should I send a bug report? What is your rationale for including it? lspci is hardly an essential tool (although it _is_ highly useful of course, but so are a couple of 100 other tools that are not included)... Correct place to file a bug report would be the pseudo package base, but I strongly suggest you do not file a bug for this. Wrong, see above. Since the install-report template requests the output of lspci, I would think you -- of all folks -- would want it as part of the base system. Imho, installation-reports should depend on, or recommend lspci if it requires its output for the report. Thanks -- ·''`. If I can't dance to it, it's not my revolution : :' :-- Emma Goldman `. `' Proudly running Debian GNU/Linux (unstable) `- www.amayita.com www.malapecora.com www.chicasduras.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#388159: missing lspci on a fresh install
Processing commands for [EMAIL PROTECTED]: reassign 388159 installation-reports Bug#388159: missing lspci on a fresh install Bug reassigned from package `base' to `installation-reports'. retitle 388159 installation-reports: Please depend on lspci Bug#388159: missing lspci on a fresh install Changed Bug title. severity wishlist Unknown command or malformed arguments to command. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#388159: missing lspci on a fresh install
On Tue, Sep 19, 2006 at 11:25:21AM +0200, Amaya wrote: reassign 388159 installation-reports retitle 388159 installation-reports: Please depend on lspci severity wishlist thanks Hi Amaya, ... Rick Thomas wrote: Package: base Please do not file bugs against the base pseudo-package. It is there just as a catch-all-I-dunno-where-to-file-this-report for users that can't really tell what package is giving them problems. All the bug reports here get reassigned to the right package. it was Frans who suggested this, and doing ping-pong of bug reporters is hardly user friendly, especially given the rather crude kind of response Guy and Rick are getting. Since the install-report template requests the output of lspci, I would think you -- of all folks -- would want it as part of the base system. Imho, installation-reports should depend on, or recommend lspci if it requires its output for the report. Installation-reports is always installed, right ? or would there be need of another bug report against another yet-to-be-determined package for inclusion of lspci in either the base system or the server task ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Processed: Re: Bug#388159: missing lspci on a fresh install
severity 388159 wishlist stop On Tue, Sep 19, 2006, Debian Bug Tracking System wrote: severity wishlist Unknown command or malformed arguments to command. -- Loïc Minier [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Processed: Re: Bug#388159: missing lspci on a fresh install
Processing commands for [EMAIL PROTECTED]: severity 388159 wishlist Bug#388159: installation-reports: Please depend on lspci Severity set to `wishlist' from `normal' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#388159: missing lspci on a fresh install
I feel my previous email could be taken as harsh on my side, which it was not menat to be at all. I apologize to the reporter if he feels this way. Sven Luther wrote: it was Frans who suggested this, and doing ping-pong of bug reporters is hardly user friendly I am not doing ping pong of anything. This bug was incorrectly assigned to the base pseudo-package, which I co-maintain with Dato, so it is my duty to reassign it to where I think it belongs. Of course I could be wrong and it might be reassigned again to a more suited package and I see no problem with it. especially given the rather crude kind of response Guy and Rick are getting. Despite whatever empathy I might feel or not about this issue, I don't see how letting this bug rot in the wrong place can be more polite, useful or fulfilling for the bug reporter. Regards... and Happy and productive discussion/hacking to all involved! (Please keep me out this loop) -- ·''`. If I can't dance to it, it's not my revolution : :' :-- Emma Goldman `. `' Proudly running Debian GNU/Linux (unstable) `- www.amayita.com www.malapecora.com www.chicasduras.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Processed: Re: Bug#388159: missing lspci on a fresh install
Processing commands for [EMAIL PROTECTED]: severity 388159 wishlist Bug#388159: installation-reports: Please depend on lspci Severity set to `wishlist' from `wishlist' stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#388159: missing lspci on a fresh install
On Tue, Sep 19, 2006 at 12:19:57PM +0200, Amaya wrote: I feel my previous email could be taken as harsh on my side, which it was not menat to be at all. I apologize to the reporter if he feels this way. :) Sven Luther wrote: it was Frans who suggested this, and doing ping-pong of bug reporters is hardly user friendly I am not doing ping pong of anything. This bug was incorrectly assigned to the base pseudo-package, which I co-maintain with Dato, so it is my duty to reassign it to where I think it belongs. It was done so on Frans suggestion. Of course I could be wrong and it might be reassigned again to a more suited package and I see no problem with it. I will let the installation-report maintainer comment, but as this is a d-i packages, ... Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: missing lspci on a fresh install
On Mon, Sep 18, 2006 at 02:44:40PM +0100, David Goodenough wrote: On Monday 18 September 2006 14:13, Frans Pop wrote: On Monday 18 September 2006 14:56, De Leeuw Guy wrote: I just finish a new net-install with the daily builds 20060918 of testing. I have a strange bug with the network after the first reboot. lo become eth0 eth0 become eth1_temp and I cannot access the network. Known issue. Upgrade to udev from unstable. I try to start lspci to identify my network card but this tools missing. Then install pci-utils... That does not help if you are trying to identify the network card in order to set up the install and you wanting to do a network install. The only alternative here is to reboot using Knoppix or the like and see what it finds, then restart the Debian install. You can also look at /sys or /proc/pci and /proc/bus/pci directly, it has all the info :) Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
missing lspci on a fresh install
Hello all I just finish a new net-install with the daily builds 20060918 of testing. I have a strange bug with the network after the first reboot. lo become eth0 eth0 become eth1_temp and I cannot access the network. I try to start lspci to identify my network card but this tools missing. Regards Guy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: missing lspci on a fresh install
On Monday 18 September 2006 14:56, De Leeuw Guy wrote: I just finish a new net-install with the daily builds 20060918 of testing. I have a strange bug with the network after the first reboot. lo become eth0 eth0 become eth1_temp and I cannot access the network. Known issue. Upgrade to udev from unstable. I try to start lspci to identify my network card but this tools missing. Then install pci-utils... Cheers, FJP pgpwuxjgKaxVg.pgp Description: PGP signature
Re: missing lspci on a fresh install
Frans Pop a écrit : Known issue. Upgrade to udev from unstable. How can I do that without network access ? Then install pci-utils... Ok, but why this tool are not on the base-system ? Cheers, FJP Thanks for your respons Guy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: missing lspci on a fresh install
On Monday 18 September 2006 14:13, Frans Pop wrote: On Monday 18 September 2006 14:56, De Leeuw Guy wrote: I just finish a new net-install with the daily builds 20060918 of testing. I have a strange bug with the network after the first reboot. lo become eth0 eth0 become eth1_temp and I cannot access the network. Known issue. Upgrade to udev from unstable. I try to start lspci to identify my network card but this tools missing. Then install pci-utils... That does not help if you are trying to identify the network card in order to set up the install and you wanting to do a network install. The only alternative here is to reboot using Knoppix or the like and see what it finds, then restart the Debian install. David Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: missing lspci on a fresh install
On Monday 18 September 2006 15:39, De Leeuw Guy wrote: Frans Pop a écrit : Known issue. Upgrade to udev from unstable. How can I do that without network access ? Use another machine to download the package and a USB stick to move it to your machine the install using 'dpkg -i'? Then install pci-utils... Ok, but why this tool are not on the base-system ? The d-i team is not responsible for what is part of the base system and what is not. You can also find the info from lspci in /var/log/installer/hardware-suppary (or something like that). pgpArmh40wSDW.pgp Description: PGP signature
Re: missing lspci on a fresh install
Thanks, I follow the procedure from this link : http://www.mail-archive.com/debian-boot@lists.debian.org/msg77135.html and work now. Guy Frans Pop a écrit : On Monday 18 September 2006 15:39, De Leeuw Guy wrote: Frans Pop a écrit : Known issue. Upgrade to udev from unstable. How can I do that without network access ? Use another machine to download the package and a USB stick to move it to your machine the install using 'dpkg -i'? Then install pci-utils... Ok, but why this tool are not on the base-system ? The d-i team is not responsible for what is part of the base system and what is not. You can also find the info from lspci in /var/log/installer/hardware-suppary (or something like that). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: missing lspci on a fresh install
On Sep 18, 2006, at 10:17 AM, De Leeuw Guy wrote: Frans Pop a écrit : The d-i team is not responsible for what is part of the base system and what is not. Then who is? Where should I send a bug report?
Re: missing lspci on a fresh install
On Monday 18 September 2006 21:49, Rick Thomas wrote: On Sep 18, 2006, at 10:17 AM, De Leeuw Guy wrote: Frans Pop a écrit : The d-i team is not responsible for what is part of the base system and what is not. Then who is? Where should I send a bug report? What is your rationale for including it? lspci is hardly an essential tool (although it _is_ highly useful of course, but so are a couple of 100 other tools that are not included)... Correct place to file a bug report would be the pseudo package base, but I strongly suggest you do not file a bug for this. pgpHlvikxoBQG.pgp Description: PGP signature
Re: missing lspci on a fresh install
Hello Rick, Frans Rick Thomas a écrit : On Sep 18, 2006, at 10:17 AM, De Leeuw Guy wrote: Frans Pop a écrit : The d-i team is not responsible for what is part of the base system and what is not. Then who is? Where should I send a bug report? Yes, I'am surprising also about this kind of respons, I make this post just to report a problem, for me it's abnormal that the lspci are not available on the base system. And in conjunction with my udev problem I'am on the black night (solved by the post of Geert). Another question : where I post this kind of report ? If debian-boot is not the good place, ok, sorry for the disturb, but where ? Guy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: missing lspci on a fresh install
Hello Frans Correct place to file a bug report would be the pseudo package base, but I strongly suggest you do not file a bug for this. I not consider that is a bug, but an essential functionality that are missing just after a bad reboot. Regards Guy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: missing lspci on a fresh install
On Monday 18 September 2006 23:26, De Leeuw Guy wrote: I not consider that is a bug, but an essential functionality that are missing just after a bad reboot. No it is not as the installer has already saved the info in /var/log/installer/. And even after a bad reboot it is hardly essential (highly useful, yes). pgpnoz5MR7StK.pgp Description: PGP signature
Re: missing lspci on a fresh install
Package: base On Sep 18, 2006, at 4:57 PM, Frans Pop wrote: On Monday 18 September 2006 21:49, Rick Thomas wrote: On Sep 18, 2006, at 10:17 AM, De Leeuw Guy wrote: Frans Pop a écrit : The d-i team is not responsible for what is part of the base system and what is not. Then who is? Where should I send a bug report? What is your rationale for including it? lspci is hardly an essential tool (although it _is_ highly useful of course, but so are a couple of 100 other tools that are not included)... Correct place to file a bug report would be the pseudo package base, but I strongly suggest you do not file a bug for this. This has been discussed before. Since the install-report template requests the output of lspci, I would think you -- of all folks -- would want it as part of the base system. As things stand, it gets dragged in most of the time because the Desktop task needs it. But if I chose to do a minimal install without including the Desktop task (say for example because I just want to test a new part of the debian installer and I don't want to wait for the whole Desktop task to get installed) well, lspci isn't there. Another use case for including pci-utils (the parent package of lspci) in the base-system is for a server install, where the Desktop task is not likely to be wanted, but the utilities in pci-utils are likely to be needed. But, as you point out, The d-i team is not responsible for what is part of the base system and what is not. So I'll just submit a bug report to base and let those who *are* responsible sort it out.
Re: missing lspci on a fresh install
On Mon, Sep 18, 2006 at 11:24:17PM +0200, De Leeuw Guy wrote: Rick Thomas a écrit : On Sep 18, 2006, at 10:17 AM, De Leeuw Guy wrote: Frans Pop a écrit : The d-i team is not responsible for what is part of the base system and what is not. Then who is? Where should I send a bug report? Yes, I'am surprising also about this kind of respons, I make this post just to report a problem, for me it's abnormal that the lspci are not available on the base system. And in conjunction with my udev problem I'am on the black night (solved by the post of Geert). Another question : where I post this kind of report ? If debian-boot is not the good place, ok, sorry for the disturb, but where ? I assume that the pointer to package 'base' has been seen. base is what the computer does need to boot. The computer can start without the lspci program, but it can't without a shell nor other essential programms. In other words: Install the package pciutils if you want the lspci tool Guy HtH GSt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: missing lspci on a fresh install
On Mon, Sep 18, 2006 at 10:57:24PM +0200, Frans Pop wrote: On Monday 18 September 2006 21:49, Rick Thomas wrote: On Sep 18, 2006, at 10:17 AM, De Leeuw Guy wrote: Frans Pop a écrit : The d-i team is not responsible for what is part of the base system and what is not. Then who is? Where should I send a bug report? What is your rationale for including it? lspci is hardly an essential tool (although it _is_ highly useful of course, but so are a couple of 100 other tools that are not included)... Correct place to file a bug report would be the pseudo package base, but I strongly suggest you do not file a bug for this. You can't have it both ways, you can't argue on one side that you are not responsible for it, and then give such recomendations as above. Still hurting, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
