Bug 613360

Summary:	sys-apps/portage-9999: --usepkg does not work when the corresponding ebuild is not longer available
Product:	Portage Development	Reporter:	Zac Medico <zmedico>
Component:	Core - Interface (emerge)	Assignee:	Portage team <dev-portage>
Status:	RESOLVED FIXED
Severity:	normal	CC:	esigra
Priority:	Normal	Keywords:	InVCS
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	612960, 619102

Description Zac Medico gentoo-dev

2017-03-20 23:26:55 UTC

Since the fix for bug 612960, the behavior for emerge --usepkg has changed for cases where an atom can only be satisfied by a binary package that would be masked by the --use-ebuild-visiblity option.

For example, a command like this used to succeed for a package where a binary package was available but the corresponding ebuild was not longer available:

# emerge --usepkg =app-misc/foo-3

[binary     U  ] app-misc/foo-3

Since commit e309323f156528a8a79a1f755e1326e8880346b7, it fails as follows:

# emerge --usepkg =app-misc/foo-3

!!! All ebuilds that could satisfy "=app-misc/foo-3" have been masked.
!!! One of the following masked packages is required to complete your request:
- app-misc/foo-3::test_repo (masked by: )

Comment 1 Zac Medico gentoo-dev

2017-03-21 00:07:17 UTC

Patch posted for review:

https://archives.gentoo.org/gentoo-portage-dev/message/6959716d3572bad50444224c9a6fa212
https://github.com/gentoo/portage/pull/144

Comment 2 Zac Medico gentoo-dev

2017-03-22 09:02:16 UTC

This is in the master branch:

https://gitweb.gentoo.org/proj/portage.git/commit/?id=82bfd91325b052a4c9250a04939641c15b3d2a20