Created attachment 305987 [details] emerge --info Starting with udev-181 a new dependency to kmod was introduced to the udev package. See bug# 402175 for details. With module-init-tools-3.16-r1 introduced also a dependency that kmod is not allowed to be installed (!sys-apps/kmod). The module-init-tools are part of the @system layout and therefore it's not possible to simply remove them. Next time you run a 'emerge -vuD --newuse world' it will be included again. [blocks B ] sys-apps/kmod ("sys-apps/kmod" is blocking sys-apps/module-init-tools-3.16-r1) [blocks B ] sys-apps/module-init-tools ("sys-apps/module-init-tools" is blocking sys-apps/kmod-7) * Error: The above package list contains packages which cannot be * installed at the same time on the same system. (sys-apps/kmod-7::gentoo, ebuild scheduled for merge) pulled in by >=sys-apps/kmod-5 required by (sys-fs/udev-182::gentoo, ebuild scheduled for merge) (sys-apps/module-init-tools-3.16-r1::gentoo, ebuild scheduled for merge) pulled in by sys-apps/module-init-tools required by @system So it looks like a deadlock situation.
virtual/modutils is part of the @system, not module-init-tools directly, so simply: emerge -C module-init-tools emerge -1 kmod
I've tried that already and ended up with the same error. When I do a 'emerge -vuD --newuse world' the module-init-tools are still included because they are still part of @system. [ebuild U ] sys-fs/udev-182 [171-r5] USE="openrc%* rule_generator -build -debug -doc% -floppy -gudev -hwdb -introspection -keymap (-selinux) -static-libs% (-acl%*) (-action_modeswitch%) (-edd%) (-extras%) (-test%)" 774 kB [blocks B ] sys-apps/kmod ("sys-apps/kmod" is blocking sys-apps/module-init-tools-3.16-r1) [blocks B ] sys-apps/module-init-tools ("sys-apps/module-init-tools" is blocking sys-apps/kmod-7) Total: 20 packages (15 upgrades, 3 new, 1 in new slot, 1 reinstall), Size of downloads: 99,456 kB Conflict: 2 blocks (2 unsatisfied) * Error: The above package list contains packages which cannot be * installed at the same time on the same system. (sys-apps/kmod-7::gentoo, installed) pulled in by >=sys-apps/kmod-5 required by (sys-fs/udev-182::gentoo, ebuild scheduled for merge) (sys-apps/module-init-tools-3.16-r1::gentoo, ebuild scheduled for merge) pulled in by sys-apps/module-init-tools required by @system
1) Post the output of 'emerge -pvDNut world' after 'emerge -C module-init-tools' and 'emerge -1 kmod' 2) Add sys-apps/module-init-tools to /etc/portage/package.mask and do 1) again
I think I found it, you have profile pointed to /usr/portage: Portage 2.1.10.49 (!/usr/portage/profiles/default/linux/amd64/10.0 But PORTDIR is set to /srv/portage: PORTDIR="/srv/gentoo/portage" This would imply you are not using correct profiles and they are out of date.
Set your profile to a directory where your PORTDIR is to ensure it gets updated too when you update your Portage tree. Closing.
Yes, you're right. I've moved my portage folder to an NFS share and set the PORTDIR variable accordingly. Unfortunately I've forgot to change the make.profile symlink in the etc directory. Retesting now.
Problem vanished. ;-) Thanks for your help!
