home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   linux.debian.kernel      Debian kernel discussions      2,884 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 2,537 of 2,884   
   Vincent Danjean to All   
   Bug#1126896: firmware-nvidia-graphics: C   
   03 Feb 26 15:10:01   
   
   XPost: linux.debian.bugs.dist   
   From: vdanjean@debian.org   
      
   Package: firmware-nvidia-graphics   
   Version: 20251021-1~bpo13+1   
   Severity: minor   
      
     Hi,   
      
     On most of my systems, I've APT Pin files in order to get the linux kernel   
   and related packages (firmware, etc.) from backports.   
   Recently, I tried to upgrade an up-to-date boorworm (with backports for the   
   kernel+firmware) to trixie (with backports for the kernel+firmware).   
   It fails with the following message:   
   Preparing to unpack .../252-firmware-nvidia-graphics_20251021-1~   
   po13+1_all.deb ...   
   dpkg-maintscript-helper: error: file '/usr/lib/firmware/nvidia/ad103' not   
   owned by package 'firmware-nvidia-graphics'   
   dpkg-maintscript-helper: error: file '/usr/lib/firmware/nvidia/ad103/gsp' not   
   owned by package 'firmware-nvidia-graphics'   
   dpkg-maintscript-helper: error: directory '/usr/lib/firmware/nvidia/ad103'   
   contains files not owned by package firmware-nvidia-graphics, ca   
   nnot switch to symlink   
   dpkg: error processing archive /tmp/apt-dpkg-install-JfnTpC/252-   
   irmware-nvidia-graphics_20251021-1~bpo13+1_all.deb (--unpack):   
    new firmware-nvidia-graphics package pre-installation script subprocess   
   returned error exit status 1   
      
     At this time, firmware-nvidia-graphics 20250410-2~bpo12+1 was installed.   
      
     I know that bookwork-backports -> trixie-backports is not officially   
   supported, hence the minor severity. I think the problem comes from the mix of   
   "dir-to-symlink change of nvidia/ad10{3,4,6,7}" [09624635e929] and the   
   usrmerge operation.   
     I fixed this by temporary removing the package and re-installing it after.   
   I initially tried to manually install firmware packages from trixie (and not   
   trixie-backports) and then upgrading to trixie-backports but I messed up   
   in the apt command line and removed the package...   
      
     I'm not sure if you want to try to support this non-standard upgrade path.   
   If not, this bug report will just document this behavior and a possible   
   workaround. If I've time, I will check if upgrading to trixie before   
   trixie-backports also work.   
      
     Regards,   
       Vincent   
      
   -- System Information:   
   Debian Release: 13.3   
     APT prefers stable-updates   
     APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990,   
   'stable'), (500, 'oldstable-updates'), (500, 'oldstable-security'), (500,   
   'oldstable')   
   Architecture: amd64 (x86_64)   
      
   Kernel: Linux 6.17.13+deb13-amd64 (SMP w/8 CPU threads; PREEMPT)   
   Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set   
   Shell: /bin/sh linked to /usr/bin/dash   
   Init: systemd (via /run/systemd/system)   
      
   firmware-nvidia-graphics depends on no packages.   
      
   firmware-nvidia-graphics recommends no packages.   
      
   Versions of packages firmware-nvidia-graphics suggests:   
   ii  initramfs-tools  0.148.3   
      
   -- no debconf information   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca