When defining a package to exclude during an update and there's a portage update to be done, the emerge process fails when resuming after portage has been updated. Reproducible: Always Steps to Reproduce: 1. emerge -avuDN @world --exclude mysql Actual Results: These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] sys-apps/portage-2.2_rc78 [2.2_rc77] USE="-build -doc -epydoc -python3 (-selinux)" LINGUAS="-pl" 140 kB *** Portage will stop merging at this point and reload itself, then resume the merge. [ebuild R ] dev-libs/glib-2.24.1-r1 USE="fam -debug -doc (-selinux) -xattr (-hardened%)" 5,208 kB [ebuild U ] dev-java/icedtea6-bin-1.9 [1.8.1-r1] USE="X alsa nsplugin -doc -examples -source" 34,950 kB [ebuild U ] net-wireless/bluez-4.69 [4.66-r1] USE="alsa consolekit cups usb -caps -debug -gstreamer -maemo6% -old-daemons -pcmcia -test-programs" 975 kB Total: 4 packages (3 upgrades, 1 reinstall), Size of downloads: 41,272 kB Would you like to merge these packages? [Yes/No] >>> Verifying ebuild manifests >>> Starting parallel fetch >>> Emerging (1 of 4) sys-apps/portage-2.2_rc78 >>> Installing (1 of 4) sys-apps/portage-2.2_rc78 >>> Jobs: 0 of 4 complete Load avg: 2.11, 1.64, 1.40 * Messages for package sys-apps/portage-2.2_rc78: * If you always want to use the latest development version of portage * please read http://www.gentoo.org/proj/en/portage/doc/testing.xml * Usage: emerge [options] emerge: error: Invalid Atom(s) in --exclude parameter: '['mysql']' (only package names and slot atoms (with widlcards) allowed) Expected Results: Portage just resumes and continues the update as usual. There is also an typo in the error message: Currently: emerge: error: Invalid Atom(s) in --exclude parameter: '['mysql']' (only package names and slot atoms (with widlcards) allowed) Corrected: emerge: error: Invalid Atom(s) in --exclude parameter: '['mysql']' (only package names and slot atoms (with wildcards) allowed)
This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=74d344ca49331ee866371f08b5f41eed9b9279c0
This is fixed in 2.1.9.3 and 2.2_rc79.