Insane libegl1 package in stretch-backports?

[stevepusser]

Does it want to nuke your system by removing hundreds of packages like it would mine?

[emariz]

Could an strict dependency version from Gnome Session or Xorg be the culprit?
This is its reverse dependency on my Testing system.

Code: Select all

$ aptitude --display-format '%c %M %p' --disable-columns search '?installed ?depends(libegl1)'

i A gnome-session-bin                                        
i A gstreamer1.0-plugins-bad
i A libcogl20
i A libegl1-mesa
i A libgstreamer-plugins-bad1.0-0
i A libmutter-1-0
i A libqt5gui5
i A libwayland-egl1-mesa
i A libwebkit2gtk-4.0-37
i A xserver-xorg-core
i A xwayland

[stevepusser]

I think it's because some of the sister packages from its source, libglvnd, break Mesa egl packages << 17.2, and a lot of packages depend on that for the Stretch Mesa 13.0.6.

I have the same libglvnd backport builds in my experimental Mesa backport repo, and they work there because I have Mesa 17.3.6.

[Head_on_a_Stick]

Does it want to nuke your system by removing hundreds of packages like it would mine?

No:

Code: Select all

root@alpine:~# apt install libegl1/stretch-backports
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Selected version '1.0.0-2~bpo9+1' (Debian Backports:stretch-backports [amd64]) for 'libegl1'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libegl1 : Depends: libegl-mesa0 but it is not installable or
                    libegl-vendor but it is not installable
E: Unable to correct problems, you have held broken packages.
root@alpine:~#

But if I use `aptitude` then it does offer to remove most things as the second choice.

Does this need a bug report then?

[stevepusser]

Probably an email on the backports mailing list is the better way to do it. It came up because I accidentally had my experimental Mesa repo attached to pbuilder when I backported ring from buster, and it automatically added that libegl1 dependency to the GUI. So I tried to install it from backports to see if that would help....no. I fixed it by rebuilding ring without that repo attached.