Created attachment 276141 [details] create_ebuild_with_unsupported_EAPI `emerge` fails to find ebuilds masked by EAPI when repository is specified. The attached script creates example ebuilds. $ PORTDIR_OVERLAY="/tmp/test_repository" emerge -Op =app-misc/test-0 These are the packages that would be merged, in order: [ebuild N ] app-misc/test-0 $ PORTDIR_OVERLAY="/tmp/test_repository" emerge -Op =app-misc/test-0::test_repository These are the packages that would be merged, in order: [ebuild N ] app-misc/test-0 $ PORTDIR_OVERLAY="/tmp/test_repository" emerge -Op =app-misc/test-1 These are the packages that would be merged, in order: !!! All ebuilds that could satisfy "=app-misc/test-1" have been masked. !!! One of the following masked packages is required to complete your request: - app-misc/test-1::test_repository (masked by: EAPI 5) The current version of portage supports EAPI '4'. You must upgrade to a newer version of portage before EAPI masked packages can be installed. For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. $ PORTDIR_OVERLAY="/tmp/test_repository" emerge -Op =app-misc/test-1::test_repository These are the packages that would be merged, in order: emerge: there are no ebuilds to satisfy "=app-misc/test-1::test_repository".
This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=c067704f25f8ef74e53d16a333067767b69e06dd
This is fixed in 2.1.10.1 and 2.2.0_alpha39.