The way it is presently done, it also masks the newer versions from my local overlay. Observe: "!!! The following installed packages are masked: - dev-python/python-sipsimple-3.1.1::local (masked by: package.mask) /usr/portage/profiles/package.mask: # Pacho Ramos <pacho@gentoo.org> (14 Jul 2017) # Buggy, doesn't compile for a long time, bug #575772. Removal in a month. - net-voip/blink-3.0.3::local (masked by: package.mask) For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook." So, the only versions that should be masked are the ones in the portage official tree Reproducible: Always
Suggested fix: =dev-python/python-sipsimple-2.5.1-r3 =net-voip/blink-1.4.1
https://packages.gentoo.org/packages/net-voip/blink
We are never specifying concrete versions and listing every ebuild un package.masks for removing. You should be able to unmask it from your overlay And I am completely against now forcing treecleaners to mask every concrete version in the package.masks entries
(In reply to Pacho Ramos from comment #3) > We are never specifying concrete versions and listing every ebuild in > package.mask for removing. That may be the right approach when masking deprecated packages but not when masking unmaintained ones with active upstream. > You should be able to unmask it from your overlay. I was aware of that. However this is merely a nuisance and it's not worth bothering. > And I am completely against now forcing treecleaners to mask every concrete > version in the package.mask entries No forcing should be necessary, an updated guideline should suffice.
