https://github.com/Heather/gentoo-gnome/blob/master/profiles/package.unmask This file is defining its own unmasks for the repo. This is the 1st issue of this ticket. Isn't that a bad style having repos unmasking or accepting their own elements? The 2nd issue of this ticket is that I wondered that any /etc/portage/package.mask/* with */*::gnome-next is just ignored. I set this line for every inoccifial overlay for not updating implicitly version packages from the overlay. This seems more like a portage bug, that overlay profiles have precedence over /etc/portage/ . If so I would split this 2nd issue into a separate bug report. Reproducible: Always
2nd issue about "Overlays package.unmask overwriting local package.mask" separated to bug 624936.
Hello > Isn't that a bad style having repos unmasking or accepting their own elements? Questionable, in my opinion masking new packages in main tree is bad style. I suggest to open discussions about that and another resources on this github repository: https://github.com/Heather/gentoo-gnome
Forwarded upstream: https://github.com/Heather/gentoo-gnome/issues/205
