Christopher Cowart <ccowart <at> rescomp.berkeley.edu> writes:
> Sounds like this is related to the bug that's in an earlier thread. > Do as root: > # ebuild `equery which udev` digest >>> Generating digest file... <<< udev-079.tar.bz2 >>> Generating manifest file... <<< ChangeLog <<< files/05-udev-early.rules-078 <<< files/05-udev-early.rules-079 <<< files/digest-udev-068-r1 <<< files/digest-udev-069 <<< files/digest-udev-070-r1 <<< files/digest-udev-071 <<< files/digest-udev-072 <<< files/digest-udev-073 <<< files/digest-udev-077 <<< files/digest-udev-077-r1 <<< files/digest-udev-077-r2 <<< files/digest-udev-077-r3 <<< files/digest-udev-077-r4 <<< files/digest-udev-077-r5 <<< files/digest-udev-078 <<< files/digest-udev-079 <<< files/digest-udev-079-r1 <<< files/digest-udev-081 <<< files/digest-udev-081-r1 <<< files/digest-udev-084 <<< files/udev-021-udev_add_c-gcc295-compat.patch <<< files/udev-050-udev_volume_id.patch <<< files/udev-parisc-path_id-again.patch <<< files/udev-parisc-path_id.patch <<< files/udev-start-077-r2.sh <<< files/udev-start-077-r4.sh <<< files/udev-start-077.sh <<< files/udev-start-079.sh <<< files/udev-start.sh <<< files/udev-stop.sh <<< files/udev.conf <<< files/udev.conf.post_024 <<< files/udev.conf.post_046 <<< files/udev.conf.post_050 <<< files/udev.conf.post_059 <<< files/udev.conf.post_081 <<< files/udev.hotplug.empty <<< files/udev.permissions <<< files/udev.rules <<< files/udev.rules-018 <<< files/udev.rules-064-r1 <<< files/udev.rules-077 <<< files/udev.rules-077-r1 <<< files/udev.rules-077-r5 <<< files/udev.rules-078 <<< files/udev.rules-084 <<< files/udev.rules.post_012 <<< metadata.xml <<< udev-068-r1.ebuild <<< udev-069.ebuild <<< udev-070-r1.ebuild <<< udev-071.ebuild <<< udev-072.ebuild <<< udev-073.ebuild <<< udev-077-r1.ebuild <<< udev-077-r2.ebuild <<< udev-077-r3.ebuild <<< udev-077-r4.ebuild <<< udev-077-r5.ebuild <<< udev-077.ebuild <<< udev-078.ebuild <<< udev-079-r1.ebuild <<< udev-079.ebuild <<< udev-081-r1.ebuild <<< udev-081.ebuild <<< udev-084.ebuild >>> Computed message digests. > This will update the digest for now. The changes will be overwritten the > next time you sync portage, but it won't matter til the next time you > emerge udev. At which time, hopefully they'll have it fixed in portage. WEll in 'unmerge' the udev, so now I have to keep the system online until an emerge sync brings a new, installable udev. I even tried to got back to udev-079, but that would not install either.... ideas? which bug do I watch for resolution? James -- gentoo-user@gentoo.org mailing list