[gentoo-user] Do I need to do anything if a package masked by my profile?

[James Stevenson]

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 <matt...@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

[Dale]

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

:-)  :-) 

[Neil Bothwick]

On Mon, 11 Jun 2018 10:06:36 +0100, James Stevenson wrote:

> 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 <matt...@gentoo.org> (10 Jun 2018)
> # Packages combined into x11-base/xorg-proto.
> #All reverse deps transitioned.
> # Removal in 30 days. Bug #656250

You shouldn't have any of these packages installed now, they should have
been depcleaned after xorg-proto was installed. If depclean doesn't
remove them, they still be required by a package in an overlay, that
happened to me.

emerge -cpv packagename

should tell you why each package is still there.


--
Neil Bothwick

WinErr 014: Keyboard locked - Try anything you can think of.

[James Stevenson]

Thank you for the advice, you've both been very helpful! I'll take a look at it this evening.

James

[John Blinka]

You shouldn't have any of these packages installed now, they should have
been depcleaned after xorg-proto was installed. If depclean doesn't
remove them, they still be required by a package in an overlay, that
happened to me.

emerge -cpv packagename

should tell you why each package is still there.

In my case, depclean didn’t remove them after xorg-proto was installed, no other package depended on them, and there were no portage anomalies like being accidentally included in my world file.  I had to remove them explicitly by hand.  Don’t know what that’s all about, but everything still works.

John Blinka

[Donald Johnson]

On Mon, Jun 11, 2018 at 4:36 AM, Neil Bothwick <ne...@digimed.co.uk> wrote:
> emerge -cpv packagename

Oddly enough, I ran that command, and it looks like all of those
packages are required by media-libs/mesa-17.3.9. Now I'm curious...

~Donny Johnson

[Donald Johnson]

Nevermind. Referring to the "x11-proto/dri2proto masked but still
needed by media-libs/mesa" thread, looks like re-emerging mesa fixed the
issue.

~Donny Johnson