Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #91042 > unrolled thread

Bug#1126896: firmware-nvidia-graphics: Cannot upgrade from bookworm-backports to trixie-backports

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1126896: firmware-nvidia-graphics: Cannot upgrade from bookworm-backports to trixie-backports Vincent Danjean <vdanjean@debian.org> - 2026-02-03 15:10 +0100
    Processed: Re: Bug#1126896: firmware-nvidia-graphics: Cannot  upgrade from bookworm-backports to trixie-backports "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-02-27 00:00 +0100
    Bug#1126896: firmware-nvidia-graphics: Cannot upgrade from bookworm-backports to trixie-backports Ben Hutchings <ben@decadent.org.uk> - 2026-02-27 00:00 +0100

#91042 — Bug#1126896: firmware-nvidia-graphics: Cannot upgrade from bookworm-backports to trixie-backports

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~bpo13+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-firmware-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

[toc] | [next] | [standalone]

#91440 — Processed: Re: Bug#1126896: firmware-nvidia-graphics: Cannot upgrade from bookworm-backports to trixie-backports

Processing control commands:

> tag -1 wontfix
Bug #1126896 [firmware-nvidia-graphics] firmware-nvidia-graphics: Cannot upgrade from bookworm-backports to trixie-backports
Added tag(s) wontfix.

-- 
1126896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126896
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#91441

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 wontfix

On Tue, 2026-02-03 at 14:54 +0100, Vincent Danjean wrote:
> 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~bpo13+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-firmware-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.
[...]

Indeed, we are trying to do a dir-to-symlink conversion under
/usr/lib/firmware but when the preinst script runs the installed files
are all in /lib/firmware still.

dpkg-maintscript-helper isn't sophisticated enough to handle this, and
currently the maintainer scripts are assembled from templates, so fixing
this would require significant effort, not to mention the time to test
the multiple possible upgrade paths.

Since as you say bookworm-backport -> trixie-backports is not documented
as supported, I'm going to leave this unfixed.

Ben.

-- 
Ben Hutchings
Always try to do things in chronological order;
it's less confusing that way.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web