James Stevenson wrote: > Hi all, > > I was running `emerge --update --newuse --deep @world` this morning and > I received a notification that one of my packages had been masked by my > profile. Am I correct in thinking that this issue will resolve itself in > 30 days? > > !!! The following installed packages are masked: > - x11-proto/xextproto-7.3.0-r1::gentoo (masked by: package.mask) > /usr/portage/profiles/package.mask: > # Matt Turner <matts...@gentoo.org> (10 Jun 2018) > # Packages combined into x11-base/xorg-proto. > #All reverse deps transitioned. > # Removal in 30 days. Bug #656250 > > - x11-proto/dri2proto-2.8-r2::gentoo (masked by: package.mask) > - x11-proto/xf86driproto-2.1.1-r2::gentoo (masked by: package.mask) > - x11-proto/dri3proto-1.0-r1::gentoo (masked by: package.mask) > - x11-proto/presentproto-1.1-r1::gentoo (masked by: package.mask) > - x11-proto/xf86vidmodeproto-2.3.1-r2::gentoo (masked by: package.mask) > - x11-proto/glproto-1.4.17-r2::gentoo (masked by: package.mask) > For more information, see the MASKED PACKAGES section in the emerge > man page or refer to the Gentoo Handbook. > > All the best, > James > >
If my memory serves me correctly, the package you have installed now is being included/transitioned in another package. In other words, you should be able to uninstall xextproto and the files that were in it are now in xorg-proto. It may be that you have to emerge xextproto again or it may even require a USE flag change to insure it creates the new files from the old package. If my memory has failed me, I'm sure someone will come along and correct me. ;-) Dale :-) :-)
