After syncing to the latest portage tree, "emerge -uDN world" wants to emerge sys-fs/static-dev-0.1-r2 (marked as a new package). Pulled in by virtual/dev-manager. Pre-emerge check fails: "Cannot install on udev/devfs tmpfs." Reproducible: Always Actual Results: * Messages for package sys-fs/static-dev-0.1-r2: * We have detected that you currently use udev or devfs or devtmpfs * and this ebuild cannot install to the same mount-point. * ERROR: sys-fs/static-dev-0.1-r2::gentoo failed (pretend phase): * Cannot install on udev/devfs tmpfs. * * Call stack: * ebuild.sh, line 127: Called pkg_pretend * static-dev-0.1-r2.ebuild, line 35: Called abort * static-dev-0.1-r2.ebuild, line 19: Called die * The specific snippet of code: * die "Cannot install on udev/devfs tmpfs."
Created attachment 757122 [details] emerge --info '=sys-fs/static-dev-0.1-r2::gentoo'
I suspect you've got sys-fs/udev masked unnecessarily so it pulls in a rather fringe provider of the virtual. See the eudev news item.
Could you share emerge -p -uvDU @world and grep -rsin "udev" /etc/portage
Thank you for the hints. Actually, the systems affected had sys-fs/udev masked. Unmasked it, emerge would install udev instead of eudev. No need for sys-fs/static-dev. Thanks again.