Created attachment 385058 [details] emerge --info Running portage-2.2.13: $ emerge eix $ FEATURES="unmerge-backup" emerge -C eix ... >>> Unmerging in: 5 4 3 2 1 >>> Unmerging (1 of 1) app-portage/eix-0.29.3... /usr/bin/python2.7: can't open file '/usr/lib/portage/python2.7/quickpkg': [Errno 2] No such file or directory ... Where quickpkg really is: $ qlist sys-apps/portage | grep quickpkg /usr/bin/quickpkg /usr/lib/python-exec/python2.7/quickpkg Falling back to portage-2.2.8-r1 resolves the issue.
Created attachment 385150 [details, diff] _quickpkg_dblink: fix bug #523152 This fixes the unmerge-backup and downgrade-backup features to be compatible with the new setup.py quickpkg install location, while preserving compatibility for running from a source tree (for unit tests or developement purposes). If not running from a source tree, then the PATH variable is used to locate the quickpkg binary. I'll be maintaining this patch in the following branch: https://github.com/zmedico/portage/tree/bug_523152
(In reply to Zac Medico from comment #1) > I'll be maintaining this patch in the following branch: > > https://github.com/zmedico/portage/tree/bug_523152 Now it's fixed to use X_OK instead of EX_OK.
This is in git now: https://github.com/gentoo/portage/commit/f31405557db59f7127a8bbeea52da36172a4b75b
Released in portage2.2.14_rc1