On Sat, Apr 18, 2020 at 06:57:14AM +0100, Ashley Dixon wrote > On Fri, Apr 17, 2020 at 10:25:14PM -0400, Walter Dnes wrote: > > Setting up to do my monthly update <G>. There was an update to > > portage, so I ran it. The final stage (install) complained about a > > missing (python?) module named "netlink". Is this a serious problem? > > I can't immediately see why portage would require this; I have the > same version of you and it compiles fine without netlink. > Nonetheless, try emerging dev-python/netlink. > > What are your portage USE-flags ?
PYTHON_TARGETS="python2_7 python3_6" PYTHON_SINGLE_TARGET="python3_6" Wait a minute. Looking at the error message in more detail, I see "/usr/lib64/python2.7/site-packages/portage/process.py" is the file complaining. No complaints from python 3.6. I tried turning off python 2.7 for portage in package.use... sys-apps/portage -python_single_target_python2_7 -rsync-verify ...and the portage install was short and sweet. ======================================================================== >>> Installing (1 of 1) sys-apps/portage-2.3.89-r2::gentoo * Using python3.6 in global scope * Setting make.globals default DISTDIR="/usr/portage/distfiles" for backward compatibility * Setting repos.conf default location = /usr/portage for backward compatibility >>> Auto-cleaning packages... >>> No outdated packages were found on your system. * GNU info directory index is up-to-date ======================================================================== After doing the update, I'll remove "python2_7" from make.conf, re-update, and see what breaks, and requires "python_single_target_python2_7" in package.use. -- Walter Dnes <[email protected]> I don't run "desktop environments"; I run useful applications
