Re: mesa-libgallium:amd64=26.1.2-1~bpo13+1 Breaks mesa-va-drivers (< 25.2.8-3)

Simon McVittie <[email protected]> Wed, 15 Jul 2026 09:34:07 +0100
Newsgroups gmane.linux.debian.devel.x,gmane.linux.debian.backports.general
Message-ID <[email protected]>
On Tue, 14 Jul 2026 at 18:39:00 -0500, Alexandra wrote:
>I saw that mesa-libgallium and its associated packages were updated in 
>trixie-backports without mesa-va-drivers being updated, causing 
>unsatisfied dependencies.

Do I assume correctly that the unsatisfied dependency you're referring 
to is:

     va-driver-all -Depends-> mesa-va-drivers

or is there another?

>I figured this is a known issue, but I 
>wanted to put it out there.

mesa-libgallium Provides mesa-va-drivers (and mesa-vdpau-drivers), so it 
should be able to satisfy those dependencies. However, apt won't always 
realise that a "real" package can be replaced by a virtual package.

If the Provides isn't enough for smooth upgrades, then it might be 
necessary for the maintainers of mesa to restore the mesa-va-drivers and 
mesa-vdpau-drivers binary packages as empty transitional packages that 
depend on mesa-libgallium, and backport that change to trixie-backports. 
If this is done, the transitional packages should be kept until after 
the trixie release, at which point they can be removed.

Transitional packages are often necessary, or at least desirable, when 
several binary packages get merged into one (case #6 on 
https://wiki.debian.org/PackageTransition).

     smcv