# emerge sys-fs/udev Calculating dependencies ...done! >>> emerge (1 of 1) sys-fs/udev-030 to / >>> md5 files ;-) udev-024-r1.ebuild >>> md5 files ;-) ChangeLog >>> md5 files ;-) metadata.xml >>> md5 files ;-) udev-025-r1.ebuild >>> md5 files ;-) udev-026-r1.ebuild >>> md5 files ;-) udev-027.ebuild >>> md5 files ;-) udev-028.ebuild >>> md5 files ;-) udev-029.ebuild >>> md5 files ;-) udev-030.ebuild >>> md5 files ;-) udev-031.ebuild >>> md5 files ;-) files/digest-udev-024-r1 >>> md5 files ;-) files/digest-udev-025-r1 >>> md5 files ;-) files/digest-udev-026-r1 >>> md5 files ;-) files/digest-udev-027 >>> md5 files ;-) files/digest-udev-028 >>> md5 files ;-) files/digest-udev-029 >>> md5 files ;-) files/digest-udev-030 >>> md5 files ;-) files/digest-udev-031 >>> md5 files ;-) files/udev-016-logging-config-option.patch >>> md5 files ;-) files/udev-015-no-wait-for-sleep.patch >>> md5 files ;-) files/udev-021-udev_add_c-gcc295-compat.patch >>> md5 files ;-) files/udev-017-no-wait-for-sleep.patch >>> md5 files ;-) files/udev-018-sysfs-build-fix.patch >>> md5 files ;-) files/udev-019-unlink-existing.patch !!! File is corrupt or incomplete. (Digests do not match) >>> our recorded digest: ab89de7957a7c7e6435203022d1db98a >>> your file's digest: 233bf645719657d9b8265f34a66d20e2 !!! File does not exist: /usr/portage/sys-fs/udev/files/udev.conf >>> Please ensure you have sync'd properly. Please try 'emerge sync' and >>> optionally examine the file(s) for corruption. A sync will fix most cases. FEATURES="autoaddcvs ccache sandbox sfperms strict userpriv usersandbox" Yea, using strict is why I receive that message, but this error would not have to happen.
Should now be fixed.
