When I try to mask a package with ambiguous name portage ignores /etc/portage/package.mask For example trying to mask mldonkey by adding it to package.mask has no result. Reproducible: Always Steps to Reproduce: 1.emerge -p "ambiguous-packet", portage will tell about de ambiguous ebuild and ask for more detail. 2.add one of the possible ambiguous ebuild to package.mask 3.try to emerge the masked ebuild Actual Results: Portage ignored that the ebuild was masked in /etc/portage/package.mask and installed the packet. Expected Results: Portage should take care about /etc/portage/package.mask and not emerge the ebuild I have tested it with mldonkey. If you try to emerge mldonkey, portage will ask you to try to emerge net-p2p/mldonkey or app-emacs/mldonkey. In this case neither of the ebuilds can be masked by adding them to /etc/portage/packages.mask I don't know if the same occurs for package.unmask.
Reopen with the output from emerge --info and attach /etc/portage/package.mask as a text/plain.
