On Wed, May 01, 2019 at 05:26:07PM +0100, Simon McVittie wrote: > Control: retitle -1 xserver-xorg-core: transitively depends on libgl1-mesa-dri > > On Wed, 01 May 2019 at 15:42:23 +0200, Jonas Smedegaard wrote: > > Quoting Jonas Smedegaard (2019-05-01 15:25:16) > > > xserver-xorg-core 2:1.19.3-2 has Depends: libgl1-mesa-glx | libgl > > > > > > xserver-xorg-core 2:1.19.4-1 has Depends: libgl > > (The former is correct, but the latter should say libgl1, not libgl) > > I don't think this is a bug. libgl1-mesa-glx was an implementation of > the abstract libgl interface. Xorg now depends on libgl1, which is a > vendor-neutral dispatcher that loads one of several backends, including > Mesa's: because it's vendor-neutral, there is no longer any need for > alternatives. > > libgl1-mesa-glx is now a transitional package which pulls in libgl1 > and libglx-mesa0, and (indirectly) libgl1-mesa-dri, so adding it as > an alternative would not help to make libgl1-mesa-dri more optional. > > > Seems the change coincide with the introduction of src:libglvnd. > > libgl1-mesa-glx | libgl dependencies being replaced by libgl1 is part > of the GLVND transition, but would not necessarily cause the symptom of > a transitive dependency on libgl1-mesa-dri. > > I think that might actually be caused by: > > mesa (17.2.0~rc6-1) experimental; urgency=medium > ... > * control: Bump libgl1-mesa-dri to libglx-mesa0 Depends, it's needed > for swrast used on some tests. > > If I'm correct about that, then this bug should perhaps be reassigned to > libglx-mesa0. > > Perhaps it should be those tests that explicitly pull in libgl1-mesa-dri? > > (Although I do question how useful libglx-mesa0 can possibly be without > the DRI drivers that make it work.) > Thanks Simon. I don't think there's a bug here in either xserver or mesa.
Cheers, Julien
