Pentoo: Masked mesa and don't know how to fix

Message

resill · Post by **resill** » Thu Aug 09, 2018 4:01 pm

Hi all,,

First of all, I'm on Pentoo but I'm guessing this is a (basic) package masking issue for which I lack the know-how to fix it myself

Basically I cannot upgrade my system because of a masking issue:

Code: Select all

➜  ~ sudo emerge -DUauv --autounmask=y --keep-going --with-bdeps=y @world

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!

!!! All ebuilds that could satisfy ">=media-libs/mesa-9.1.6[opencl,abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,
abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]" have been masked.
!!! One of the following masked packages is required to complete your request:
- media-libs/mesa-9999::gentoo (masked by: missing keyword)
- media-libs/mesa-18.1.5::gentoo (masked by: ~amd64 keyword)
- media-libs/mesa-18.1.4::gentoo (masked by: ~amd64 keyword)
- media-libs/mesa-18.0.5::gentoo (masked by: ~amd64 keyword)

(dependency required by "virtual/opencl-0-r5::gentoo" [ebuild])
(dependency required by "app-crypt/hashcat-4.2.0::gentoo" [ebuild])
(dependency required by "pentoo/pentoo-cracking-2018.2-r4::pentoo[pentoo-full,opencl]" [ebuild])
(dependency required by "pentoo/pentoo-2015.1::pentoo[cracking]" [installed])
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.

➜  ~

I tried manually adding the ~amd64 keyword to any of the mesa versions mentioned above, but then the same message would return. When the same message above returns, it no longer shows the manually masked version but it still mentions the remaining versions and I'm not sure this is the right way to go about it.

So, sorry again if I need to to open a GitHub issue on https://github.com/pentoo/pentoo-overlay, but I still suspect I just lack an understanding how to properly mask packages. Would anyone like to help a newbie out?

[Moderator edit: broke long whitespace-free lines in code tags to fix thread layout. -Hu]

eccerr0r · Post by **eccerr0r** » Thu Aug 09, 2018 8:16 pm

Yeah this is somewhat distribution specific as the Gentoo tree, mesa-17 is stable which according to your text, doesn't exist in Pentoo.

Well in normal Gentoo these auto-unmasks get written to etc-update/dispatch-conf files. You'll need to run one of these two to actually unmask the ebuild.

The question is: how did you unmask/keyword the package -- what file did you use?

In the normal Gentoo install, the keywording would belong in /etc/portage/package.keywords

=media-libs/mesa-18.0.5 ~amd64

Post by **NeddySeagoon** » Thu Aug 09, 2018 9:09 pm

resill,

If you understood what

Code: Select all

 --autounmask=y

does, you wouldn't use it.

Portage isn't very good at making decisions for you that you really need to make yourself. This feature, used repeatedly can dig you a very big hole.
Portage claims that you need a testing version of mesa.
The real question is why?

I suspect that you have other testing packages installed that you are not telling us about.

Telling portage to try harder might help.

Code: Select all

emerge -DUauv --backtrack=50 --keep-going --with-bdeps=y @world

is worth trying.
Read the man page and see what it says about --autounmask and --backtrack

Post by **NeddySeagoon** » Thu Aug 09, 2018 9:11 pm

Moved from Portage & Programming to Unsupported Software.

Pentoo is not Gentoo, so its not officially supported.
That does not mean you won't get help.

resill · Post by **resill** » Fri Aug 10, 2018 7:22 am

@NeddySeagoon,

Thanks for your reply. Please refer to the following output with --backtrack=50:

Code: Select all

➜  ~ sudo emerge -DUauv --backtrack=50 --keep-going --with-bdeps=y @world

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!

!!! All ebuilds that could satisfy ">=media-libs/mesa-9.1.6[opencl,
    abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,
    abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,
    abi_s390_32(-)?,abi_s390_64(-)?]" have been masked.
!!! One of the following masked packages is required to complete your request:
- media-libs/mesa-9999::gentoo (masked by: missing keyword)
- media-libs/mesa-18.1.5::gentoo (masked by: ~amd64 keyword)
- media-libs/mesa-18.1.4::gentoo (masked by: ~amd64 keyword)
- media-libs/mesa-18.0.5::gentoo (masked by: ~amd64 keyword)

(dependency required by "virtual/opencl-0-r5::gentoo" [ebuild])
(dependency required by "app-crypt/hashcat-4.2.0::gentoo" [ebuild])
(dependency required by "pentoo/pentoo-cracking-2018.2-r4::pentoo[pentoo-full,opencl]" [ebuild])
(dependency required by "pentoo/pentoo-2015.1::pentoo[cracking]" [installed])
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.

➜  ~

Increasing the integer tenfold also did not make a difference.

I read the manpage and it mentions that --autounmask is already enabled by default on Gentoo, correct? On (hardened) Pentoo it is not and whenever I needed dependencies that were masked, I needed to provide the --autounmask option so that it would prompt me to write change to package.accept_keywords. But perhaps this is not the way to go about it as it would dig me a very big hole as you say?

Wrapped a long line to make the forum layout behave. —Chiitoo

Post by **fedeliallalinea** » Fri Aug 10, 2018 7:58 am

You can post your emerge --info, emerge -pv mesa and also emerge -pv =media-libs/mesa-17.3.9?

resill · Post by **resill** » Fri Aug 10, 2018 8:36 am

@fedeliallalinea,

Certainly!

emerge --info: https://pastebin.com/geeTJAN9
emerge -pv mesa: https://pastebin.com/pbvG6k8H
emerge -pv '=media-libs/mesa-17.3.9': https://pastebin.com/ePu8GUkc

Post by **fedeliallalinea** » Fri Aug 10, 2018 8:57 am

The problem is that pentoo has masked opencl use flag for mesa

pentoo/base/package.use.mask wrote:#mesa only supports opencl for radeon users, but that doesn't allow password cracking, etc, so makes no sense for us
media-libs/mesa opencl

then your assumption

resill wrote:First of all, I'm on Pentoo but I'm guessing this is a (basic) package masking issue

is incorrect, problem is only pentoo related .

Now you have two option

remove all opencl dependencies
or unmask opencl use flag with /etc/portage/profile/package.use.mask

resill · Post by **resill** » Fri Aug 10, 2018 6:59 pm

Not sure why I would remove 'opencl', but to humor you I added 'media-libs/mesa -opencl' to '/etc/portage/profile/package.use.mask'.

Code: Select all

➜  ~ cat /etc/portage/profile/package.use.mask
media-libs/mesa -opencl
➜  ~ sudo emerge -DUauv --backtrack=50 --keep-going --with-bdeps=y @world
                                                                     
These are the packages that would be merged, in reverse order:

Calculating dependencies \

!!! Problem resolving dependencies for media-libs/mesa from @selected                     ... done!

!!! The ebuild selected to satisfy "media-libs/mesa" has unmet requirements.
- media-libs/mesa-17.3.9::gentoo USE="classic dri3 egl gallium gbm gles2 llvm nptl opencl pic vaapi vdpau xa -bindist -d3d9 -debug -gles1 -openmax -osmesa -pax_kernel (-selinux) -unwind -valgrind -vulkan -wayland -xvmc" ABI_X86="32 (64) (-x32)" VIDEO_CARDS="(-freedreno) -i915 -i965 (-imx) -intel -nouveau -r100 -r200 -r300 -r600 -radeon -radeonsi (-vc4) -virgl (-vivante) -vmware"

  The following REQUIRED_USE flag constraints are unsatisfied:
    opencl? ( any-of ( video_cards_r600 video_cards_radeonsi ) )

  The above constraints are a subset of the following complete expression:
    d3d9? ( dri3 gallium ) llvm? ( gallium ) opencl? ( gallium llvm any-of ( video_cards_r600 video_cards_radeonsi ) ) openmax? ( gallium ) gles1? ( egl ) gles2? ( egl ) vaapi? ( gallium ) vdpau? ( gallium ) vulkan? ( any-of ( video_cards_i965 video_cards_radeonsi ) video_cards_radeonsi? ( llvm ) ) wayland? ( egl gbm ) xa? ( gallium ) video_cards_freedreno? ( gallium ) video_cards_intel? ( classic ) video_cards_i915? ( any-of ( classic gallium ) ) video_cards_i965? ( classic ) video_cards_imx? ( gallium video_cards_vivante ) video_cards_nouveau? ( any-of ( classic gallium ) ) video_cards_radeon? ( any-of ( classic gallium ) gallium? ( x86? ( llvm ) amd64? ( llvm ) ) ) video_cards_r100? ( classic ) video_cards_r200? ( classic ) video_cards_r300? ( gallium x86? ( llvm ) amd64? ( llvm ) ) video_cards_r600? ( gallium ) video_cards_radeonsi? ( gallium llvm ) video_cards_vc4? ( gallium ) video_cards_virgl? ( gallium ) video_cards_vivante? ( gallium gbm ) video_cards_vmware? ( gallium )

(dependency required by "@selected" [set])
(dependency required by "@world" [argument])
➜  ~

I must admit I don't fully understand the problem here. Why would Pentoo mask 'opencl' for 'mesa' if this results in problems during upgrades? Is this a bug from their side, or have I been doing something wrong and I don't yet understand what exactly?

Post by **fedeliallalinea** » Fri Aug 10, 2018 7:10 pm

Code: Select all

  The following REQUIRED_USE flag constraints are unsatisfied:
    opencl? ( any-of ( video_cards_r600 video_cards_radeonsi ) )

Portage tell you that if you want opencl on mesa you should enable also video_cards_r600 or video_cards_radeonsi use flag

For remove opencl you should look what packages depends on virtual/opencl with command

Code: Select all

$ equery d virtual/opencl

you can post output if you want help.

resill · Post by **resill** » Tue Aug 14, 2018 2:38 pm

It turns out I could update my packages again when I commented out my custom VIDEO_CARDS in make.conf. Pentoo advises to set this variable to your own hardware needs to avoid compiling in unnecessary features. Not setting this assumes Pentoo defaults and it work again.