When upgrading to mesa 25.3.x, the mesa-vdpau and mesa-va packages will be removed.
The mesa-va packages have been merged into the mesa-libgallium packages, so it is okay to let mesa-va packages be removed. You will still have mesa VA-API acceleration.
The mesa-vdpau packages have been dropped upstream. Mesa devs said they had no use, but there may still be a few corner cases, such as the nouveau driver could use VDPAU to accelerate H.264 on older cards. And VLC may have trouble with VA-API if I remember correctly.
Note: This should not affect users of Nvidia proprietary driver, as that has its own VDPAU lib in libnvidia-decode-* package
Thank you for posting this, I updated without issues (excluding holding xkb-data).
Sorry, but I cannot recommend updating at this time.
Discover tells me that it wants to update:
libegl-mesa0
libgbm1
libgl1-mesa-dri
libglx-mesa0
mesa-libgallium
mesa-va-drivers
mesa-vdpau-drivers
vdpau-driver-all
BUT
apt full-install says, that:
root@pucki:/home/lw# apt full-upgrade
Aktualisiere nicht:
libegl-mesa0 libgbm1 libgl1-mesa-dri libglx-mesa0 mesa-libgallium
==> I rather stick to apt here.
Regards
@Cefdinir71
No problem for me, but I use an AMD/Radeon card.
Here is the changelog for mesa (https://metadata.ftp-master.debian.org/changelogs/main/m/mesa/mesa_25.3.2-2_changelog)-libgallium:
mesa (25.3.2-1) unstable; urgency=medium
....
[ Mario Limonciello (AMD) ]
* Merge mesa-va-drivers and mesa-vdpau-drivers into mesa-libgallium (LP: #2135270)
...
-- Timo Aaltonen Thu, 18 Dec 2025 19:03:53 +0200
Before the upgrade:
# apt install mesa-libgallium
Upgrading:
libegl-mesa0 libgl1-mesa-dri mesa-libgallium
libgbm-dev libgbm1 libglx-mesa0
REMOVING:
mesa-va-drivers mesa-vdpau-drivers vdpau-driver-all
Summary:
Upgrading: 6, Installing: 0, Removing: 3, Not Upgrading: 0
After that, restart:
# apt full-upgrade
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
@Camelot thanks for the update description. I think that is actually what Discover wants to do during updating, but the point, why i brought this up here is that apt does not seem to be aware of the fact that the update of mesa-libgallium will invoke other packages be removed without issues, I mean why apt full-upgrade does not mention thie first place and only after enforcing it to update the lib alone.
My expectation to apt would be that it dissolved newly created dependancy woes first before noting that something had to be held back because off... well I do not even know what breaks apt full-update here.