I recently upgraded from portage-2.1.2-r9 to portage-184.108.40.206 on an amd64 box. This upgrade introduced a move from /usr/lib to /usr/lib64 for many portage-related files. After refreshing my environment with `source /etc/profile; env-update` everything appeared to be working correctly, except for etc-update which failed with the following message:
~ # etc-update
/usr/sbin/etc-update: line 444: /usr/lib/portage/bin/portageq: No such file or directory
Exiting: Need write access to etc
Line 443 of /usr/sbin/etc-update:
eval $(/usr/lib/portage/bin/portageq envvar -v CONFIG_PROTECT \
CONFIG_PROTECT_MASK PORTAGE_CONFIGROOT PORTAGE_TMPDIR ROOT USERLAND)
Changing the above to point to '/usr/lib64/portage/bin/portageq' fixed the problem, but isn't an elegant solution.
We can remove the /usr/lib/portage/bin/ prefix since etc-update should be able to find portageq via path. Isn't there usually a /usr/lib -> lib64 symlink though?
This is fixed in svn r6203.
(In reply to comment #1)
>Isn't there usually a /usr/lib -> lib64 symlink
Usually yes, but hardened's basesystem is messed up in that regard.
That was a bug in the experimental 2006.0 amd64 multilib hardened stages. You can fix it by hand after unpacking, and everything works fine. I even repacked those stages over a month ago to fix that problem.
*** Bug 172015 has been marked as a duplicate of this bug. ***
This has been released in 220.127.116.11.
*** Bug 172858 has been marked as a duplicate of this bug. ***