If you are going to update pciutils on an offline system it tries to fetch the latest pci.ids from the internet anyway (and hangs forever ?). Reproducible: Always Steps to Reproduce: 1.Disconnet from Internet 2.execute 'emerge pciutils' 3. Actual Results: Calculating dependencies ...done! >>> emerge (1 of 4) sys-apps/pciutils-2.1.11-r5 to / >>> md5 files ;-) pciutils-2.1.11-r4.ebuild >>> md5 files ;-) pciutils-2.1.11-r3.ebuild >>> md5 files ;-) pciutils-2.1.11-r5.ebuild >>> md5 files ;-) files/2.1.11-sysfs.patch >>> md5 files ;-) files/pciutils-2.1.11-bsd.patch >>> md5 files ;-) files/2.1.11-scan.patch >>> md5 files ;-) files/pcimodules-pciutils-2.1.11.diff >>> md5 files ;-) files/pciutils-2.1.11-gentoo-paths.patch >>> md5 files ;-) files/digest-pciutils-2.1.11-r4 >>> md5 files ;-) files/digest-pciutils-2.1.11-r3 >>> md5 files ;-) files/2.1.11-fix-pci-ids-location-refs.patch >>> md5 files ;-) files/pciutils-2.1.11-fix-pci-ids-location-refs.patch >>> md5 files ;-) files/digest-pciutils-2.1.11-r5 >>> md5 files ;-) files/pciutils-2.1.11-sysfs.patch >>> md5 src_uri ;-) pciutils-2.1.11.tar.gz >>> md5 src_uri ;-) pci.ids-20041019.bz2 >>> Unpacking source... >>> Unpacking pciutils-2.1.11.tar.gz to /var/tmp/portage/pciutils-2.1.11-r5/work >>> Unpacking pci.ids-20041019.bz2 to /var/tmp/portage/pciutils-2.1.11-r5/work * Applying pcimodules-pciutils-2.1.11.diff ... [ ok ] * Applying pciutils-2.1.11-sysfs.patch ... [ ok ] * Applying pciutils-2.1.11-gentoo-paths.patch ... [ ok ] * Applying 2.1.11-scan.patch ... [ ok ] * Applying pciutils-2.1.11-bsd.patch ... [ ok ] * Updating pci.ids ... ... (processing hangs) Expected Results: Either skip the fetch on request or allow to place an updated pci.ids somewhere (maybe in /usr/portage/distfiles) to be taken into account.
Created attachment 68865 [details] Output of 'emerge info'
no, it'll time out
I suggest to add a message in front of "Updating pci.ids ..." stating that this may hang for several minutes (timeout) before the process continues. Here it hung for at least 2 minutes (then i aborted it).
Yeah, it times out, but it's a major PITA to have it idling around for ages before it does. Maybe some sane timeout value for the wget/curl call would be appropriate. I have been working around this issue by temporarily REJECTing outbound http traffic, but that's far from optimal solution.
whatever, forced a smaller timeout value
