Bug#1110523: mesa-vulkan-drivers: Tries to overwrite shared '/usr/share/vulkan/icd.d/asahi_icd.json'
Control: forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/13745
On Thu, 07 Aug 2025 at 13:03:18 -0300, Nelson A. de Oliveira wrote:
Unpacking mesa-vulkan-drivers:amd64 (25.2.0-1) over (25.1.7-1) ...
dpkg: error processing archive /var/cache/apt/archives/mesa-vulkan-drivers_25.2.0-1_amd64.deb (--unpack):
trying to overwrite shared '/usr/share/vulkan/icd.d/asahi_icd.json', which is different from other instances of package mesa-vulkan-drivers:amd64
This is a result of
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/35567
upstream. I already opened
https://gitlab.freedesktop.org/mesa/mesa/-/issues/13745 about this.
Short term solution suggested here:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/13745#note_3065256
when you get to packaging post-!35567 versions of Mesa for
Debian/Ubuntu, you'll need at least a stopgap solution to this.
Since the packaging is already running sed on the JSON manifest to
make the library_path architecture-independent and implement approach
(2.), probably the easiest way in the short term is to delete the
line that sets the library architecture (/library_arch/d) at the
same time, effectively undoing !35567 (merged).
I'll try to turn that into a concrete patch.
Or alternatively, reverting !35567 should do it.
The long term answer is to talk to upstream on
https://gitlab.freedesktop.org/mesa/mesa/-/issues/13745 and figure out
what long-term solution to https://bugs.debian.org/980148 they want.
There seems to be rough consensus that what we're doing is "the right
shape", but it'll likely need some more code upstream for developer
use-cases.
smcv
Reply to: