You are right - it is part of buster. And this is good news. So does it mean the bug should be closed? At least I don't see any more problems.
On Sat, Mar 11, 2023 at 9:12 PM Sebastian Ramacher <sramac...@debian.org> wrote: > > On 2023-03-11 17:51:37 +0300, Vladimir Stavrinov wrote: > > On Tue, Feb 14, 2023 at 4:13 PM Sebastian Ramacher <sramac...@debian.org> > > wrote: > > > > > > Control: reassign -1 0.0.8-1 > > > > Sorry if I don't understand something, but today I've unexpectedly > > discovered that the driver You reassigned to, that is > > nvidia-vaapi-driver, isn't installed on my system. When I've tried to > > install it I encountered the conflict: > > > > Unpacking nvidia-vaapi-driver:amd64 (0.0.8-1) ... > > dpkg: error processing archive > > /var/cache/apt/archives/nvidia-vaapi-driver_0.0.8-1_amd64.deb > > (--unpack): > > trying to overwrite > > '/usr/lib/x86_64-linux-gnu/dri/nvidia_drv_video.so', which is also in > > package vdpau-va-driver:amd64 0.7.4-7 > > > > After removing the vdpau-va-driver and installing nvidia-vaapi-driver > > the problem was gone. So although now I personally do not have this > > problem, the problem as such remains. The file being the subject of > > the conflict is the only binary code file in both packages. So I see > > the one of the two ways to solve the problem: > > > > 1. Either reassign this bug to vdpau-va-driver > > 2. Or remove vdpau-va-driver from the repository and change > > accordingly all being affected packages dependency to point to > > nvidia-vaapi-driver. > > vdpau-va-driver was removed from the archive in August 2019 and is > neither part of bullseye and bookworm. > > Cheers > -- > Sebastian Ramacher -- ### Vladimir Stavrinov ###
