Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED] Why updating pulls wayland
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
egrep
n00b
n00b


Joined: 16 Jul 2020
Posts: 49

PostPosted: Sat Jul 18, 2020 8:49 am    Post subject: [SOLVED] Why updating pulls wayland Reply with quote

Hello,

I'm trying to update packages and get waylyand conflict:
Code:

$ sudo emerge --ask --update --deep --with-bdeps=y --newuse @world

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

Calculating dependencies... done!
[ebuild  N     ] dev-lang/rust-bin-1.44.1  USE="-clippy -doc -rustfmt" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="sse2"
[ebuild  N     ] dev-libs/wayland-protocols-1.20
[ebuild   R    ] media-libs/mesa-20.1.3  USE="wayland*"
[ebuild   R    ] x11-libs/gtk+-3.24.21  USE="wayland*"
[ebuild     U  ] dev-libs/libdazzle-3.36.0 [3.34.1]
[ebuild   R    ] dev-qt/qtgui-5.15.0  USE="wayland*"
[ebuild  N     ] dev-qt/qtx11extras-5.15.0  USE="-debug -test"
[ebuild  N     ] dev-qt/qtdeclarative-5.15.0  USE="jit widgets -debug -gles2-only -localstorage -test -vulkan"
[ebuild  N     ] dev-qt/qtwayland-5.15.0  USE="X -debug -test -vulkan"
[ebuild     U  ] net-im/telegram-desktop-2.1.20 [2.1.18]

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

x11-libs/gtk+:3

  (x11-libs/gtk+-3.24.21:3/3::gentoo, installed) USE="X colord cups introspection (-aqua) -broadway -cloudprint -examples -gtk-doc -test -vim-syntax -wayland -xinerama" ABI_X86="(64) -32 (-x32)" pulled in by
    >=x11-libs/gtk+-3.22.0:3[X,wayland=] required by (gnome-base/gnome-control-center-3.36.4:2/2::gentoo, installed) USE="bluetooth cups gnome-online-accounts ibus networkmanager systemd -debug (-elogind) -flickr -kerberos -test -v4l -wayland" ABI_X86="(64)" INPUT_DEVICES="-wacom"
                               ^^^^^^^^                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  (x11-libs/gtk+-3.24.21:3/3::gentoo, ebuild scheduled for merge) USE="X colord cups introspection wayland (-aqua) -broadway -cloudprint -examples -gtk-doc -test -vim-syntax -xinerama" ABI_X86="(64) -32 (-x32)" pulled in by
    x11-libs/gtk+:3[X?,wayland] required by (net-im/telegram-desktop-2.1.20:0/0::gentoo, ebuild scheduled for merge) USE="X alsa dbus gtk hunspell pulseaudio spell -enchant -libressl" ABI_X86="(64)"
                       ^^^^^^^                                                                                                                                                                                                                                                                                                                                                                                                         


It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.


The following USE changes are necessary to proceed:
 (see "package.use" in the portage(5) man page for more details)
# required by net-im/telegram-desktop-2.1.20::gentoo
# required by @selected
# required by @world (argument)
>=dev-qt/qtgui-5.15.0 wayland
# required by net-im/telegram-desktop-2.1.20::gentoo[gtk]
# required by @selected
# required by @world (argument)
>=x11-libs/gtk+-3.24.21 wayland
# required by x11-libs/gtk+-3.24.21::gentoo[wayland]
# required by net-im/telegram-desktop-2.1.20::gentoo[gtk]
# required by @selected
# required by @world (argument)
>=media-libs/mesa-20.1.3 wayland



I updated USE flags but still no luck:
Code:

$ cat /etc/portage/package.use/x
x11-libs/gtk+ -wayland
media-libs/mesa -wayland



Is that related to the wayland USE flag? Am I doing something wrong? How to avoid pulling wayland?


Last edited by egrep on Sat Jul 25, 2020 11:50 am; edited 1 time in total
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 24654
Location: here

PostPosted: Sat Jul 18, 2020 1:22 pm    Post subject: Reply with quote

Try to remove wayland use flag to net-im/telegram-desktop
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
egrep
n00b
n00b


Joined: 16 Jul 2020
Posts: 49

PostPosted: Sat Jul 18, 2020 2:07 pm    Post subject: Reply with quote

fedeliallalinea wrote:
Try to remove wayland use flag to net-im/telegram-desktop


As I can see this has no effect:

Code:

$ sudo USE="-wayland" emerge --ask --oneshot --verbose-conflicts =net-im/telegram-desktop-2.1.20

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

Calculating dependencies... done!
[ebuild  N     ] dev-libs/wayland-protocols-1.20
[ebuild   R    ] media-libs/mesa-20.1.3  USE="wayland*"
[ebuild   R    ] dev-qt/qtgui-5.15.0  USE="wayland*"
[ebuild  N     ] dev-qt/qtx11extras-5.15.0  USE="-debug -test"
[ebuild   R    ] x11-libs/gtk+-3.24.21  USE="wayland*"
[ebuild  N     ] dev-qt/qtdeclarative-5.15.0  USE="jit widgets -debug -gles2-only -localstorage -test -vulkan"
[ebuild  N     ] dev-qt/qtwayland-5.15.0  USE="X -debug -test -vulkan"
[ebuild     U  ] net-im/telegram-desktop-2.1.20 [2.1.18]

The following USE changes are necessary to proceed:
 (see "package.use" in the portage(5) man page for more details)
# required by net-im/telegram-desktop-2.1.20::gentoo
# required by @selected
# required by @world (argument)
>=dev-qt/qtgui-5.15.0 wayland
# required by net-im/telegram-desktop-2.1.20::gentoo[gtk]
# required by @selected
# required by @world (argument)
>=x11-libs/gtk+-3.24.21 wayland
# required by x11-libs/gtk+-3.24.21::gentoo[wayland]
# required by net-im/telegram-desktop-2.1.20::gentoo[gtk]
# required by @selected
# required by @world (argument)
>=media-libs/mesa-20.1.3 wayland


The same with package.use file:

Code:

$ cat /etc/portage/package.use/x
x11-libs/gtk+ -wayland
media-libs/mesa -wayland
net-im/telegram-desktop -wayland

Code:

$ sudo emerge --ask --update --deep --with-bdeps=y --newuse @world

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

Calculating dependencies... done!
[ebuild  N     ] dev-libs/wayland-protocols-1.20
[ebuild   R    ] media-libs/mesa-20.1.3  USE="wayland*"
[ebuild  N     ] dev-qt/qtx11extras-5.15.0  USE="-debug -test"
[ebuild   R    ] x11-libs/gtk+-3.24.21  USE="wayland*"
[ebuild     U  ] dev-libs/libdazzle-3.36.0 [3.34.1]
[ebuild   R    ] sys-boot/grub-2.05_alpha20200310  GRUB_PLATFORMS="-pc*"
[ebuild   R    ] dev-qt/qtgui-5.15.0  USE="wayland*"
[ebuild  N     ] dev-qt/qtdeclarative-5.15.0  USE="jit widgets -debug -gles2-only -localstorage -test -vulkan"
[ebuild  N     ] dev-qt/qtwayland-5.15.0  USE="X -debug -test -vulkan"
[ebuild     U  ] net-im/telegram-desktop-2.1.20 [2.1.18]

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

x11-libs/gtk+:3

  (x11-libs/gtk+-3.24.21:3/3::gentoo, installed) USE="X colord cups introspection (-aqua) -broadway -cloudprint -examples -gtk-doc -test -vim-syntax -wayland -xinerama" ABI_X86="(64) -32 (-x32)" pulled in by
    >=x11-libs/gtk+-3.22.0:3[X,wayland=] required by (gnome-base/gnome-control-center-3.36.4:2/2::gentoo, installed) USE="bluetooth cups gnome-online-accounts ibus networkmanager systemd -debug (-elogind) -flickr -kerberos -test -v4l -wayland" ABI_X86="(64)" INPUT_DEVICES="-wacom"
                               ^^^^^^^^                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  (x11-libs/gtk+-3.24.21:3/3::gentoo, ebuild scheduled for merge) USE="X colord cups introspection wayland (-aqua) -broadway -cloudprint -examples -gtk-doc -test -vim-syntax -xinerama" ABI_X86="(64) -32 (-x32)" pulled in by
    x11-libs/gtk+:3[X?,wayland] required by (net-im/telegram-desktop-2.1.20:0/0::gentoo, ebuild scheduled for merge) USE="X alsa dbus gtk hunspell pulseaudio spell -enchant -libressl" ABI_X86="(64)"
                       ^^^^^^^                                                                                                                                                                                                                                                                                                                                                                                                         


It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously.  If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously.

For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.


The following USE changes are necessary to proceed:
 (see "package.use" in the portage(5) man page for more details)
# required by net-im/telegram-desktop-2.1.20::gentoo
# required by @selected
# required by @world (argument)
>=dev-qt/qtgui-5.15.0 wayland
# required by net-im/telegram-desktop-2.1.20::gentoo[gtk]
# required by @selected
# required by @world (argument)
>=x11-libs/gtk+-3.24.21 wayland
# required by x11-libs/gtk+-3.24.21::gentoo[wayland]
# required by net-im/telegram-desktop-2.1.20::gentoo[gtk]
# required by @selected
# required by @world (argument)
>=media-libs/mesa-20.1.3 wayland



At the end, telegram has no wayland use flag:

Code:

$ equ net-im/telegram-desktop
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for net-im/telegram-desktop-2.1.20:
 U I
 + + X          : Add support for X11
 + + alsa       : Add support for media-libs/alsa-lib (Advanced Linux Sound Architecture)
 + + dbus       : Enable dbus support for anything that needs it (gpsd, gnomemeeting, etc)
 - - enchant    : Enable the app-text/aspell spell-checking backend
 + + gtk        : Add support for x11-libs/gtk+ (The GIMP Toolkit)
 + - hunspell   : Enable the app-text/hunspell spell-checking backend
 - - libressl   : Use dev-libs/libressl instead of dev-libs/openssl when applicable (see also the ssl useflag)
 + + pulseaudio : Add support for PulseAudio sound server
 + + spell      : Add dictionary support
Back to top
View user's profile Send private message
sebB
l33t
l33t


Joined: 02 Mar 2011
Posts: 778
Location: S.O. France

PostPosted: Sat Jul 18, 2020 3:08 pm    Post subject: Reply with quote

net-im/telegram-desktop: bump to 2.1.20 wayland is not optional anymore.
Back to top
View user's profile Send private message
Ionen
Veteran
Veteran


Joined: 06 Dec 2018
Posts: 1259

PostPosted: Sat Jul 18, 2020 3:37 pm    Post subject: Reply with quote

This happened with a few other packages as well and may become more common, they end up using libraries/things from wayland even when used on non-wayland and it become required either way. The option to disable isn't always there and working around it would require rewriting parts of the code making this a upstream issue (or non-issue as they'd more likely see it as).

On the other hand of things, I'm sure wayland users would want to be able to get rid of X11 libraries too :)
Back to top
View user's profile Send private message
egrep
n00b
n00b


Joined: 16 Jul 2020
Posts: 49

PostPosted: Sat Jul 18, 2020 4:57 pm    Post subject: Reply with quote

Thanks a lot for the clarification. Especially sebB
Back to top
View user's profile Send private message
egrep
n00b
n00b


Joined: 16 Jul 2020
Posts: 49

PostPosted: Mon Jul 20, 2020 11:03 am    Post subject: Reply with quote

There is a bug report https://bugs.gentoo.org/733234
Back to top
View user's profile Send private message
iandoug
Guru
Guru


Joined: 11 Feb 2005
Posts: 599
Location: Cape Town, South Africa

PostPosted: Tue Jul 21, 2020 7:38 pm    Post subject: Reply with quote

egrep wrote:
There is a bug report https://bugs.gentoo.org/733234


Telegram says "Won't fix" and it's up to the distros to patch as necessary....
_________________
Asus Sabertooth P990, AMD FX-8150, GeForce GTX 560, 16GB Ram | Asus M3A78 64, X2 6000+, PX9800 GT, 4GB Ram | Asus M4A77TD PRO, X2 245, HD4350, 4GB RAM
Back to top
View user's profile Send private message
Ionen
Veteran
Veteran


Joined: 06 Dec 2018
Posts: 1259

PostPosted: Wed Jul 22, 2020 7:27 am    Post subject: Reply with quote

iandoug wrote:
Telegram says "Won't fix" and it's up to the distros to patch as necessary....
I don't see this happening given it means removing/changing features from the package. Even if were to give patches, in the future they may also make further use of it and it'd become a maintenance hurdle and essentially turn into a fork of the package.

At least the wayland deps will only be sitting there, not like you have to use wayland. I get that people don't like that either way though. Can stick to old version for a while but that'll surely cause problems eventually unless upstream see to it meanwhile.

Edit: Worst case could just use the -bin release, as maintainer pointed it doesn't need wayland deps (nor QT) but still seem to have its own qt+wayland stuff taking space inside it :| I had a quick look at the 2.1.20 beta binary build (on git, otherwise 2.1.13 is latest) and it's still not linked against wayland/QT stuff either so it shouldn't change with the next non-beta -bin release.
Back to top
View user's profile Send private message
iandoug
Guru
Guru


Joined: 11 Feb 2005
Posts: 599
Location: Cape Town, South Africa

PostPosted: Wed Jul 22, 2020 7:51 am    Post subject: Reply with quote

iandoug wrote:
egrep wrote:
There is a bug report https://bugs.gentoo.org/733234


Telegram says "Won't fix" and it's up to the distros to patch as necessary....


I've got this blocker at the moment, not sure if there is something else apart from Telegram causing it.
(Ignore the readline and bash, that's because I still have PHP 5 on my system and portage won't update readline)

Code:


Calculating dependencies... done!
[ebuild  N     ] media-libs/libglvnd-1.3.1::gentoo  USE="X -test" ABI_X86="32 (64) (-x32)" 698 KiB
[ebuild     U  ] sys-libs/readline-8.0_p4:0/8::gentoo [7.0_p5-r1:0/7::gentoo] USE="(split-usr) unicode -static-libs -utils" ABI_X86="32 (64) (-x32)" 2,912 KiB
[ebuild     U  ] app-shells/bash-5.0_p17::gentoo [4.4_p23-r1::gentoo] USE="net nls (readline) -afs -bashlogger -examples -mem-scramble -plugins" 9,948 KiB
[ebuild     U ~] net-im/telegram-desktop-bin-2.1.13-r1::gentoo [2.1.3::gentoo] 48,966 KiB
[blocks B      ] media-libs/mesa[-libglvnd(-)] ("media-libs/mesa[-libglvnd(-)]" is blocking media-libs/libglvnd-1.3.1)


Thanks, Ian
_________________
Asus Sabertooth P990, AMD FX-8150, GeForce GTX 560, 16GB Ram | Asus M3A78 64, X2 6000+, PX9800 GT, 4GB Ram | Asus M4A77TD PRO, X2 245, HD4350, 4GB RAM
Back to top
View user's profile Send private message
Ionen
Veteran
Veteran


Joined: 06 Dec 2018
Posts: 1259

PostPosted: Wed Jul 22, 2020 8:32 am    Post subject: Reply with quote

^ USE=libglvnd is a flag that exists on mesa, xorg-server, and (if you use it) nvidia-drivers. Gentoo enabled it on all 3 by default and needs to be changed simultaneously or else you'll get unsolvable blockers. Usually a emerge -uUD @world world update will sort it out, but you can try doing it on its own like emerge -1 nvidia-drivers mesa xorg-server (omit nvidia-drivers if need be). After the switch telegram shouldn't complaint.

If problems ensure you don't have a "-libglvnd" anywhere (enabling it is what you want here unless you're using nvidia-drivers-340), and that eselect-opengl isn't in your world file (this package is deprecated, conflicts with libglvnd, and will be removed eventually).
Back to top
View user's profile Send private message
iandoug
Guru
Guru


Joined: 11 Feb 2005
Posts: 599
Location: Cape Town, South Africa

PostPosted: Wed Jul 22, 2020 2:32 pm    Post subject: Reply with quote

Ionen wrote:
^ USE=libglvnd is a flag that exists on mesa, xorg-server, and (if you use it) nvidia-drivers. Gentoo enabled it on all 3 by default and needs to be changed simultaneously or else you'll get unsolvable blockers. Usually a emerge -uUD @world world update will sort it out, but you can try doing it on its own like emerge -1 nvidia-drivers mesa xorg-server (omit nvidia-drivers if need be). After the switch telegram shouldn't complaint.

If problems ensure you don't have a "-libglvnd" anywhere (enabling it is what you want here unless you're using nvidia-drivers-340), and that eselect-opengl isn't in your world file (this package is deprecated, conflicts with libglvnd, and will be removed eventually).



Mmmm for some reason I had -libglvnd in make.conf. Presumably because portage wanted it at some point.

The block is slightly different now, I'm not sure what the various nvidia packages are fighting about.

Code:

trooper /etc/portage/package.use #  emerge -uUDa @world

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

Calculating dependencies... done!
[ebuild     U  ] sys-libs/readline-8.0_p4 [7.0_p5-r1]
[ebuild     U  ] app-shells/bash-5.0_p17 [4.4_p23-r1]
[ebuild  N     ] media-libs/libglvnd-1.3.2  USE="X -test" ABI_X86="32 (64) (-x32)"
[ebuild   R    ] media-libs/mesa-20.0.8  USE="libglvnd*"
[blocks b      ] media-libs/mesa[-libglvnd(-)] ("media-libs/mesa[-libglvnd(-)]" is blocking media-libs/libglvnd-1.3.2)
[ebuild     U ~] net-im/telegram-desktop-bin-2.1.13-r1 [2.1.3]
[ebuild   R    ] x11-base/xorg-server-1.20.8-r1  USE="libglvnd*"
[ebuild   R    ] x11-drivers/nvidia-drivers-390.138  USE="libglvnd*"
[blocks B      ] x11-drivers/nvidia-drivers[-libglvnd(-)] ("x11-drivers/nvidia-drivers[-libglvnd(-)]" is hard blocking x11-base/xorg-server-1.20.8-r1)



 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (x11-base/xorg-server-1.20.8-r1:0/1.20.8::gentoo, ebuild scheduled for merge) pulled in by
    x11-base/xorg-server:0/1.20.8= required by (x11-drivers/xf86-input-evdev-2.10.6:0/0::gentoo, installed) USE="" ABI_X86="(64)"
    >=x11-base/xorg-server-1.18[udev] required by (x11-drivers/xf86-input-evdev-2.10.6:0/0::gentoo, installed) USE="" ABI_X86="(64)"
    x11-base/xorg-server:= required by (x11-drivers/xf86-input-evdev-2.10.6:0/0::gentoo, installed) USE="" ABI_X86="(64)"
    x11-base/xorg-server required by @selected
    <x11-base/xorg-server-1.20.99:= required by (x11-drivers/nvidia-drivers-390.138:0/390::gentoo, ebuild scheduled for merge) USE="X driver gtk3 kms libglvnd multilib tools -compat -static-libs -uvm -wayland" ABI_X86="32 (64) (-x32)"
    x11-base/xorg-server[xorg] required by (x11-drivers/xf86-input-evdev-2.10.6:0/0::gentoo, installed) USE="" ABI_X86="(64)"
    >=x11-base/xorg-server-1.15.1 required by (x11-misc/sddm-0.18.1-r1:0/0::gentoo, installed) USE="elogind pam -consolekit -systemd -test" ABI_X86="(64)"
    >=x11-base/xorg-server-1.20[udev] required by (x11-base/xorg-drivers-1.20-r2:0/0::gentoo, installed) USE="" ABI_X86="(64)" INPUT_DEVICES="evdev -elographics -joystick -libinput -synaptics -vmmouse -void -wacom" VIDEO_CARDS="nvidia -amdgpu -ast -dummy -fbdev (-freedreno) (-geode) -glint -i915 -i965 -intel -mga -nouveau -nv (-omap) -qxl -r128 -radeon -radeonsi -siliconmotion (-tegra) (-vc4) -vesa -via -virtualbox -vmware"



Thanks, Ian
_________________
Asus Sabertooth P990, AMD FX-8150, GeForce GTX 560, 16GB Ram | Asus M3A78 64, X2 6000+, PX9800 GT, 4GB Ram | Asus M4A77TD PRO, X2 245, HD4350, 4GB RAM
Back to top
View user's profile Send private message
fedeliallalinea
Bodhisattva
Bodhisattva


Joined: 08 Mar 2003
Posts: 24654
Location: here

PostPosted: Wed Jul 22, 2020 2:43 pm    Post subject: Reply with quote

Try with emerge -1 x11-base/xorg-server media-libs/mesa and then emerge -1 x11-drivers/nvidia-drivers
_________________
Questions are guaranteed in life; Answers aren't.
Back to top
View user's profile Send private message
Ionen
Veteran
Veteran


Joined: 06 Dec 2018
Posts: 1259

PostPosted: Wed Jul 22, 2020 2:55 pm    Post subject: Reply with quote

You likely had -libglvnd because nvidia-drivers-390.xx used to lack support (support is still iffy for xorg's glx but not an issue for most/non-multigpu setups).

Try emerge -1 libglvnd nvidia-drivers mesa xorg-server separately, I think telegram is confusing portage about what to do. Once the switch is done none of this should come up again.

fedeliallalinea wrote:
Try with emerge -1 x11-base/xorg-server media-libs/mesa and then emerge -1 x11-drivers/nvidia-drivers
nvidia-drivers should neither be last nor separate (unless it's not installed anyway), xorg-server has a workaround blocker for it to ensure it's rebuilt before itself (that we're seeing in action here) to prevent the glapi bug, and then those also need to be rebuilt at same time for the libglvnd switch.
Back to top
View user's profile Send private message
iandoug
Guru
Guru


Joined: 11 Feb 2005
Posts: 599
Location: Cape Town, South Africa

PostPosted: Wed Jul 22, 2020 3:23 pm    Post subject: Reply with quote

Ionen wrote:
You likely had -libglvnd because nvidia-drivers-390.xx used to lack support (support is still iffy for xorg's glx but not an issue for most/non-multigpu setups).

Try emerge -1 libglvnd nvidia-drivers mesa xorg-server separately, I think telegram is confusing portage about what to do. Once the switch is done none of this should come up again.

fedeliallalinea wrote:
Try with emerge -1 x11-base/xorg-server media-libs/mesa and then emerge -1 x11-drivers/nvidia-drivers
nvidia-drivers should neither be last nor separate (unless it's not installed anyway), xorg-server has a workaround blocker for it to ensure it's rebuilt before itself (that we're seeing in action here) to prevent the glapi bug, and then those also need to be rebuilt at same time for the libglvnd switch.


Thanks for suggestions. Above still complains... should I maybe drop out of KDE, unemerge nvidia-drivers, and try again?

Code:

# emerge -a1 libglvnd nvidia-drivers mesa xorg-server

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

Calculating dependencies... done!
[ebuild  N     ] media-libs/libglvnd-1.3.2  USE="X -test" ABI_X86="32 (64) (-x32)"
[ebuild   R    ] media-libs/mesa-20.0.8  USE="libglvnd*"
[blocks b      ] media-libs/mesa[-libglvnd(-)] ("media-libs/mesa[-libglvnd(-)]" is blocking media-libs/libglvnd-1.3.2)
[ebuild   R    ] x11-base/xorg-server-1.20.8-r1  USE="libglvnd*"
[ebuild   R    ] x11-drivers/nvidia-drivers-390.138  USE="libglvnd*"
[blocks B      ] x11-drivers/nvidia-drivers[-libglvnd(-)] ("x11-drivers/nvidia-drivers[-libglvnd(-)]" is hard blocking x11-base/xorg-server-1.20.8-r1)

 * Error: The above package list contains packages which cannot be
 * installed at the same time on the same system.

  (x11-base/xorg-server-1.20.8-r1:0/1.20.8::gentoo, ebuild scheduled for merge) pulled in by
    x11-base/xorg-server:0/1.20.8= required by (x11-drivers/xf86-input-evdev-2.10.6:0/0::gentoo, installed) USE="" ABI_X86="(64)"
    x11-base/xorg-server:= required by (x11-drivers/xf86-input-evdev-2.10.6:0/0::gentoo, installed) USE="" ABI_X86="(64)"
    >=x11-base/xorg-server-1.20[udev] required by (x11-base/xorg-drivers-1.20-r2:0/0::gentoo, installed) USE="" ABI_X86="(64)" INPUT_DEVICES="evdev -elographics -joystick -libinput -synaptics -vmmouse -void -wacom" VIDEO_CARDS="nvidia -amdgpu -ast -dummy -fbdev (-freedreno) (-geode) -glint -i915 -i965 -intel -mga -nouveau -nv (-omap) -qxl -r128 -radeon -radeonsi -siliconmotion (-tegra) (-vc4) -vesa -via -virtualbox -vmware"
    x11-base/xorg-server required by @selected
    <x11-base/xorg-server-1.20.99:= required by (x11-drivers/nvidia-drivers-390.138:0/390::gentoo, ebuild scheduled for merge) USE="X driver gtk3 kms libglvnd multilib tools -compat -static-libs -uvm -wayland" ABI_X86="32 (64) (-x32)"
    xorg-server
    x11-base/xorg-server[xorg] required by (x11-drivers/xf86-input-evdev-2.10.6:0/0::gentoo, installed) USE="" ABI_X86="(64)"
    >=x11-base/xorg-server-1.18[udev] required by (x11-drivers/xf86-input-evdev-2.10.6:0/0::gentoo, installed) USE="" ABI_X86="(64)"
    >=x11-base/xorg-server-1.15.1 required by (x11-misc/sddm-0.18.1-r1:0/0::gentoo, installed) USE="elogind pam -consolekit -systemd -test" ABI_X86="(64)"



Thanks, Ian
_________________
Asus Sabertooth P990, AMD FX-8150, GeForce GTX 560, 16GB Ram | Asus M3A78 64, X2 6000+, PX9800 GT, 4GB Ram | Asus M4A77TD PRO, X2 245, HD4350, 4GB RAM
Back to top
View user's profile Send private message
Ionen
Veteran
Veteran


Joined: 06 Dec 2018
Posts: 1259

PostPosted: Wed Jul 22, 2020 3:27 pm    Post subject: Reply with quote

Hrmm, normally I don't like to suggest it but let's force it. The way the whole depgraph for this is handled has gotten too messy I think.

Do emerge -C eselect-opengl (if still installed) then emerge -a1O libglvnd nvidia-drivers mesa xorg-server, then after that try to do a world upgrade to see if portage thinks anything is amiss. -O and -C cause portage to ignore dependency check so don't make a habit of using this as portage/ebuilds, while not perfect, are more usually right :)
Back to top
View user's profile Send private message
iandoug
Guru
Guru


Joined: 11 Feb 2005
Posts: 599
Location: Cape Town, South Africa

PostPosted: Wed Jul 22, 2020 3:50 pm    Post subject: Reply with quote

Ionen wrote:
Hrmm, normally I don't like to suggest it but let's force it. The way the whole depgraph for this is handled has gotten too messy I think.

Do emerge -C eselect-opengl (if still installed) then emerge -a1O libglvnd nvidia-drivers mesa xorg-server, then after that try to do a world upgrade to see if portage thinks anything is amiss. -O and -C cause portage to ignore dependency check so don't make a habit of using this as portage/ebuilds, while not perfect, are more usually right :)


Thanks, had already unistalled eselect-opengl.

Have video conference tonight so will try this tomorrow.

Thanks,Ian
_________________
Asus Sabertooth P990, AMD FX-8150, GeForce GTX 560, 16GB Ram | Asus M3A78 64, X2 6000+, PX9800 GT, 4GB Ram | Asus M4A77TD PRO, X2 245, HD4350, 4GB RAM
Back to top
View user's profile Send private message
Ionen
Veteran
Veteran


Joined: 06 Dec 2018
Posts: 1259

PostPosted: Wed Jul 22, 2020 4:03 pm    Post subject: Reply with quote

Sounds good to wait then yeah. That you already forcefully uninstalled eselect-opengl (I assume you used -C over -c) may have something to do with portage being confused, but following through with the rest I believe should restore order.
Back to top
View user's profile Send private message
iandoug
Guru
Guru


Joined: 11 Feb 2005
Posts: 599
Location: Cape Town, South Africa

PostPosted: Fri Jul 24, 2020 1:26 pm    Post subject: Reply with quote

Ionen wrote:
Hrmm, normally I don't like to suggest it but let's force it. The way the whole depgraph for this is handled has gotten too messy I think.

Do emerge -C eselect-opengl (if still installed) then emerge -a1O libglvnd nvidia-drivers mesa xorg-server, then after that try to do a world upgrade to see if portage thinks anything is amiss. -O and -C cause portage to ignore dependency check so don't make a habit of using this as portage/ebuilds, while not perfect, are more usually right :)


Code:


>>> Installing (1 of 4) media-libs/libglvnd-1.3.2::gentoo
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at https://bugs.gentoo.org/ unless you report exactly
 * which two packages install the same file(s). See
 * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
 * to solve the problem. And once again, please do NOT file a bug report
 * unless you have completely understood the above message.
 *
 * Detected file collision(s):
 *
 *      /usr/include/GLES/glplatform.h
 *      /usr/include/GLES/gl.h
 *      /usr/include/GLES/egl.h
 *      /usr/include/GLES/glext.h
 *      /usr/include/GL/glxext.h
 *      /usr/include/GL/glcorearb.h
 *      /usr/include/GL/glx.h
 *      /usr/include/GL/gl.h
 *      /usr/include/GL/glext.h
 *      /usr/include/GLES2/gl2platform.h
 *      /usr/include/GLES2/gl2.h
 *      /usr/include/GLES2/gl2ext.h
 *      /usr/include/KHR/khrplatform.h
 *      /usr/include/EGL/eglext.h
 *      /usr/include/EGL/eglplatform.h
 *      /usr/include/EGL/egl.h
 *      /usr/include/GLES3/gl3.h
 *      /usr/include/GLES3/gl3ext.h
 *      /usr/include/GLES3/gl3platform.h
 *      /usr/include/GLES3/gl31.h
 *      /usr/include/GLES3/gl32.h
 *      /usr/lib64/pkgconfig/egl.pc
 *      /usr/lib64/pkgconfig/gl.pc
 *      /usr/lib64/pkgconfig/glesv2.pc
 *      /usr/lib32/pkgconfig/egl.pc
 *      /usr/lib32/pkgconfig/gl.pc
 *      /usr/lib32/pkgconfig/glesv2.pc
 *      /usr/lib64/libGL.so
 *      /usr/lib64/libEGL.so.1
 *      /usr/lib64/libGLESv1_CM.so
 *      /usr/lib64/libEGL.so
 *      /usr/lib64/libGLdispatch.so
 *      /usr/lib64/libGL.so.1
 *      /usr/lib64/libGLESv2.so
 *      /usr/lib64/libGLESv2.so.2
 *      /usr/lib64/libGLdispatch.so.0
 *      /usr/lib32/libGL.so
 *      /usr/lib32/libEGL.so.1
 *      /usr/lib32/libGLESv1_CM.so
 *      /usr/lib32/libEGL.so
 *      /usr/lib32/libGLdispatch.so
 *      /usr/lib32/libGL.so.1
 *      /usr/lib32/libGLESv2.so
 *      /usr/lib32/libGLESv2.so.2
 *      /usr/lib32/libGLdispatch.so.0
 *
 * Searching all installed packages for file collisions...
 *
 * Press Ctrl-C to Stop
 *
 * media-libs/mesa-20.0.8:0::gentoo
 *      /usr/include/EGL/egl.h
 *      /usr/include/EGL/eglext.h
 *      /usr/include/EGL/eglplatform.h
 *      /usr/include/GL/gl.h
 *      /usr/include/GL/glcorearb.h
 *      /usr/include/GL/glext.h
 *      /usr/include/GL/glx.h
 *      /usr/include/GL/glxext.h
 *      /usr/include/GLES2/gl2.h
 *      /usr/include/GLES2/gl2ext.h
 *      /usr/include/GLES2/gl2platform.h
 *      /usr/include/GLES3/gl3.h
 *      /usr/include/GLES3/gl31.h
 *      /usr/include/GLES3/gl3ext.h
 *      /usr/include/GLES3/gl3platform.h
 *      /usr/include/KHR/khrplatform.h
 *
 * Package 'media-libs/libglvnd-1.3.2' NOT merged due to file collisions.
 * If necessary, refer to your elog messages for the whole content of the
 * above message.

>>> Failed to install media-libs/libglvnd-1.3.2, Log file:



I feel like I need to uninstall some stuff first ...

Code:


[I] media-libs/mesa
     Available versions:  20.0.8^t ~20.1.1^t ~20.1.2^t ~20.1.3^t ~20.1.4^t **9999*l^t {+X +classic d3d9 debug +dri3 +egl +gallium +gbm gles1 +gles2 +libglvnd +llvm lm-sensors opencl osmesa selinux test unwind vaapi valgrind vdpau vulkan vulkan-overlay wayland xa xvmc +zstd ABI_MIPS="n32 n64 o32" ABI_RISCV="lp64 lp64d" ABI_S390="32 64" ABI_X86="32 64 x32" KERNEL="linux" VIDEO_CARDS="freedreno i915 i965 intel iris lima nouveau panfrost r100 r200 r300 r600 radeon radeonsi vc4 virgl vivante vmware"}
     Installed versions:  20.0.8^t(15:53:43 30/06/2020)(X classic dri3 egl gallium gbm gles2 llvm wayland zstd -d3d9 -debug -gles1 -libglvnd -lm-sensors -opencl -osmesa -selinux -test -unwind -vaapi -valgrind -vdpau -vulkan -vulkan-overlay -xa -xvmc ABI_MIPS="-n32 -n64 -o32" ABI_RISCV="-lp64 -lp64d" ABI_S390="-32 -64" ABI_X86="32 64 -x32" KERNEL="linux" VIDEO_CARDS="-freedreno -i915 -i965 -intel -iris -lima -nouveau -panfrost -r100 -r200 -r300 -r600 -radeon -radeonsi -vc4 -virgl -vivante -vmware")
     Homepage:            https://www.mesa3d.org/ https://mesa.freedesktop.org/
     Description:         OpenGL-like graphic library for Linux



Thanks, Ian
_________________
Asus Sabertooth P990, AMD FX-8150, GeForce GTX 560, 16GB Ram | Asus M3A78 64, X2 6000+, PX9800 GT, 4GB Ram | Asus M4A77TD PRO, X2 245, HD4350, 4GB RAM
Back to top
View user's profile Send private message
Ionen
Veteran
Veteran


Joined: 06 Dec 2018
Posts: 1259

PostPosted: Fri Jul 24, 2020 1:40 pm    Post subject: Reply with quote

Temporarily force removing mesa may be simpler, you'll be re-installing it right after (emerge -C media-libs/mesa, then do the above again). This shouldn't even break installed applications given they're using libraries from nvidia-drivers rather than mesa (part of the reason this is all kind of messy, these packages provide much of the same things and USE=libglvnd changes what provides what around).

Do make double sure that USE=libglvnd is indeed getting enabled and really don't have any -libglvnd.
Back to top
View user's profile Send private message
iandoug
Guru
Guru


Joined: 11 Feb 2005
Posts: 599
Location: Cape Town, South Africa

PostPosted: Fri Jul 24, 2020 6:26 pm    Post subject: Reply with quote

Ionen wrote:
Temporarily force removing mesa may be simpler, you'll be re-installing it right after (emerge -C media-libs/mesa, then do the above again). This shouldn't even break installed applications given they're using libraries from nvidia-drivers rather than mesa (part of the reason this is all kind of messy, these packages provide much of the same things and USE=libglvnd changes what provides what around).

Do make double sure that USE=libglvnd is indeed getting enabled and really don't have any -libglvnd.


Thanks, seems to have worked, update world pulled in Telegram-bin afterwards.

Cheers, Ian
_________________
Asus Sabertooth P990, AMD FX-8150, GeForce GTX 560, 16GB Ram | Asus M3A78 64, X2 6000+, PX9800 GT, 4GB Ram | Asus M4A77TD PRO, X2 245, HD4350, 4GB RAM
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum