Bug 170178 – portage-2.1.2.2 - hardcoded /usr/lib reference in etc-update

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Josh Lamontagne 2007-03-09 21:06:30 UTC]

I recently upgraded from portage-2.1.2-r9 to portage-2.1.2.2 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.

Cheers,
Josh Lamontagne

[Comment 1 Zac Medico 2007-03-09 21:23:59 UTC]

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?

[Comment 2 Zac Medico 2007-03-10 00:09:08 UTC]

This is fixed in svn r6203.

[Comment 3 Simon Stelling (RETIRED) 2007-03-10 11:56:12 UTC]

(In reply to comment #1)
>Isn't there usually a /usr/lib -> lib64 symlink
> though?

Usually yes, but hardened's basesystem is messed up in that regard.

[Comment 4 Andrew Gaffney (RETIRED) 2007-03-10 17:03:09 UTC]

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.

[Comment 5 Zac Medico 2007-03-24 08:56:44 UTC]

*** Bug 172015 has been marked as a duplicate of this bug. ***

[Comment 6 Zac Medico 2007-03-29 22:35:52 UTC]

This has been released in 2.1.2.3.

[Comment 7 Jakub Moc (RETIRED) 2007-03-31 09:32:09 UTC]

*** Bug 172858 has been marked as a duplicate of this bug. ***