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

Groups > linux.debian.bugs.rc > #319867 > unrolled thread

Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies

Back to article view | Back to linux.debian.bugs.rc

Contents

  Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies Paul Gevers <elbrus@debian.org> - 2022-05-12 10:10 +0200
    Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies Andreas Beckmann <anbe@debian.org> - 2022-05-12 14:30 +0200
      Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies Andreas Beckmann <anbe@debian.org> - 2022-05-17 16:30 +0200
    Bug#1010883: marked as done (dkms breaks nvidia-graphics-drivers  autopkgtest on arm64: unmet dependencies) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-05-19 12:10 +0200
    Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies Andreas Beckmann <anbe@debian.org> - 2022-05-26 11:10 +0200
    Processed: Re: dkms breaks nvidia-graphics-drivers autopkgtest on  arm64: unmet dependencies "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-05-26 11:10 +0200
    Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies Andreas Beckmann <anbe@debian.org> - 2022-05-27 16:30 +0200
    Bug#1010883: marked as done (dkms: autopkgtest mixes headers from  sid and testing) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-05-27 16:50 +0200
    Processed (with 2 errors): autopkgtest fails "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-06-02 09:20 +0200
    Processed: Re: nvidia-graphics-drivers-tesla-510: fails on  ppc64el due to transitive GPL symbol usage "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-06-28 03:10 +0200

#319867 — Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies

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

Source: dkms, nvidia-graphics-drivers
Control: found -1 dkms/3.0.3-1
Control: found -1 nvidia-graphics-drivers/470.103.01-3
Severity: serious
Tags: sid bookworm
User: debian-ci@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of dkms the autopkgtest of nvidia-graphics-drivers 
fails in testing when that autopkgtest is run with the binary packages 
of dkms from unstable. It passes when run with only packages from 
testing. In tabular form:

                         pass            fail
dkms                    from testing    3.0.3-1
nvidia-graphics-drivers from testing    470.103.01-3
all others              from testing    from testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of dkms to testing 
[1]. Due to the nature of this issue, I filed this bug report against 
both packages. Can you please investigate the situation and reassign the 
bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=dkms

https://ci.debian.net/data/autopkgtest/testing/arm64/n/nvidia-graphics-drivers/21589789/log.gz

I: Removing binary package nvidia-kernel-dkms, to get clean state
I: Installing binary package nvidia-kernel-dkms
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
   glx-alternative-mesa glx-alternative-nvidia glx-diversions
   nvidia-alternative nvidia-installer-cleanup nvidia-kernel-common
   nvidia-kernel-support nvidia-modprobe update-glx
Suggested packages:
   libgl1-mesa-glx | libgl1 nvidia-driver | nvidia-driver-any
Recommended packages:
   nvidia-driver | libcuda1
The following NEW packages will be installed:
   glx-alternative-mesa glx-alternative-nvidia glx-diversions
   nvidia-alternative nvidia-installer-cleanup nvidia-kernel-common
   nvidia-kernel-dkms nvidia-kernel-support nvidia-modprobe update-glx
0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.
Need to get 25.9 MB of archives.
After this operation, 50.2 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian testing/contrib arm64 update-glx 
arm64 1.2.1 [10.6 kB]
Get:2 http://deb.debian.org/debian testing/contrib arm64 
glx-alternative-mesa arm64 1.2.1 [9912 B]
Get:3 http://deb.debian.org/debian testing/contrib arm64 
nvidia-installer-cleanup arm64 20220217+1 [19.4 kB]
Get:4 http://deb.debian.org/debian testing/contrib arm64 glx-diversions 
arm64 1.2.1 [12.6 kB]
Get:5 http://deb.debian.org/debian testing/contrib arm64 
glx-alternative-nvidia arm64 1.2.1 [10.9 kB]
Get:6 http://deb.debian.org/debian testing/non-free arm64 
nvidia-alternative arm64 470.103.01-3 [240 kB]
Get:7 http://deb.debian.org/debian testing/contrib arm64 
nvidia-kernel-common arm64 20220217+1 [10.9 kB]
Get:8 http://deb.debian.org/debian testing/contrib arm64 nvidia-modprobe 
arm64 510.68.02-1 [20.5 kB]
Get:9 http://deb.debian.org/debian testing/non-free arm64 
nvidia-kernel-support arm64 470.103.01-3 [239 kB]
Get:10 http://deb.debian.org/debian testing/non-free arm64 
nvidia-kernel-dkms arm64 470.103.01-3 [25.3 MB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 25.9 MB in 2s (16.5 MB/s)
Selecting previously unselected package update-glx.
(Reading database ... (Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 29721 files and directories currently installed.)
Preparing to unpack .../update-glx_1.2.1_arm64.deb ...
Unpacking update-glx (1.2.1) ...
Selecting previously unselected package glx-alternative-mesa.
Preparing to unpack .../glx-alternative-mesa_1.2.1_arm64.deb ...
Unpacking glx-alternative-mesa (1.2.1) ...
Selecting previously unselected package nvidia-installer-cleanup.
Preparing to unpack .../nvidia-installer-cleanup_20220217+1_arm64.deb ...
Unpacking nvidia-installer-cleanup (20220217+1) ...
Setting up nvidia-installer-cleanup (20220217+1) ...
Selecting previously unselected package glx-diversions.
(Reading database ... (Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 29866 files and directories currently installed.)
Preparing to unpack .../0-glx-diversions_1.2.1_arm64.deb ...
Unpacking glx-diversions (1.2.1) ...
Selecting previously unselected package glx-alternative-nvidia.
Preparing to unpack .../1-glx-alternative-nvidia_1.2.1_arm64.deb ...
Unpacking glx-alternative-nvidia (1.2.1) ...
Selecting previously unselected package nvidia-alternative.
Preparing to unpack .../2-nvidia-alternative_470.103.01-3_arm64.deb ...
Unpacking nvidia-alternative (470.103.01-3) ...
Selecting previously unselected package nvidia-kernel-common.
Preparing to unpack .../3-nvidia-kernel-common_20220217+1_arm64.deb ...
Unpacking nvidia-kernel-common (20220217+1) ...
Selecting previously unselected package nvidia-modprobe.
Preparing to unpack .../4-nvidia-modprobe_510.68.02-1_arm64.deb ...
Unpacking nvidia-modprobe (510.68.02-1) ...
Selecting previously unselected package nvidia-kernel-support.
Preparing to unpack .../5-nvidia-kernel-support_470.103.01-3_arm64.deb ...
Unpacking nvidia-kernel-support (470.103.01-3) ...
Selecting previously unselected package nvidia-kernel-dkms.
Preparing to unpack .../6-nvidia-kernel-dkms_470.103.01-3_arm64.deb ...
Unpacking nvidia-kernel-dkms (470.103.01-3) ...
Setting up nvidia-kernel-common (20220217+1) ...
Setting up update-glx (1.2.1) ...
Setting up nvidia-modprobe (510.68.02-1) ...
Setting up glx-alternative-mesa (1.2.1) ...
Setting up glx-diversions (1.2.1) ...
Processing triggers for glx-alternative-mesa (1.2.1) ...
Setting up glx-alternative-nvidia (1.2.1) ...
Processing triggers for glx-alternative-nvidia (1.2.1) ...
Setting up nvidia-alternative (470.103.01-3) ...
Processing triggers for nvidia-alternative (470.103.01-3) ...
Setting up nvidia-kernel-support (470.103.01-3) ...
Processing triggers for nvidia-alternative (470.103.01-3) ...
Setting up nvidia-kernel-dkms (470.103.01-3) ...
autoinstall for dkms modules has been disabled.
Processing triggers for libc-bin (2.33-7) ...
Processing triggers for update-glx (1.2.1) ...
Processing triggers for glx-alternative-nvidia (1.2.1) ...
Processing triggers for glx-alternative-mesa (1.2.1) ...
Processing triggers for libc-bin (2.33-7) ...
I: Checking for missing dkms dependency by trying to deinstall dkms
dpkg: dependency problems prevent removal of dkms:
  nvidia-kernel-dkms depends on dkms (>= 2.1.0.0).

dpkg: error processing package dkms (--remove):
  dependency problems - not removing
Errors were encountered while processing:
  dkms
I: No Linux header packages are installed. Installing all available ones:
I:   linux-headers-5.17.0-1-arm64
I:   linux-headers-5.17.0-1-cloud-arm64
I:   linux-headers-5.17.0-1-rt-arm64
I:   linux-headers-arm64
I:   linux-headers-cloud-arm64
I:   linux-headers-rt-arm64
I:   linux-headers-5.17.0-2-arm64
I:   linux-headers-5.17.0-2-cloud-arm64
I:   linux-headers-5.17.0-2-rt-arm64
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  linux-headers-5.17.0-2-arm64 : Depends: linux-kbuild-5.17 (>= 
5.17.6-1) but 5.17.3-1 is to be installed
  linux-headers-5.17.0-2-cloud-arm64 : Depends: linux-kbuild-5.17 (>= 
5.17.6-1) but 5.17.3-1 is to be installed
  linux-headers-5.17.0-2-rt-arm64 : Depends: linux-kbuild-5.17 (>= 
5.17.6-1) but 5.17.3-1 is to be installed
E: Unable to correct problems, you have held broken packages.
E: Linux headers failed to install
autopkgtest [12:19:58]: test dkms-autopkgtest

[toc] | [next] | [standalone]

#319876

On 12/05/2022 09.57, Paul Gevers wrote:
> I: No Linux header packages are installed. Installing all available ones:
> I:   linux-headers-5.17.0-1-arm64
> I:   linux-headers-5.17.0-1-cloud-arm64
> I:   linux-headers-5.17.0-1-rt-arm64
> I:   linux-headers-arm64
> I:   linux-headers-cloud-arm64
> I:   linux-headers-rt-arm64
> I:   linux-headers-5.17.0-2-arm64
> I:   linux-headers-5.17.0-2-cloud-arm64
> I:   linux-headers-5.17.0-2-rt-arm64
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>   linux-headers-5.17.0-2-arm64 : Depends: linux-kbuild-5.17 (>= 
> 5.17.6-1) but 5.17.3-1 is to be installed
>   linux-headers-5.17.0-2-cloud-arm64 : Depends: linux-kbuild-5.17 (>= 
> 5.17.6-1) but 5.17.3-1 is to be installed
>   linux-headers-5.17.0-2-rt-arm64 : Depends: linux-kbuild-5.17 (>= 
> 5.17.6-1) but 5.17.3-1 is to be installed
> E: Unable to correct problems, you have held broken packages.
> E: Linux headers failed to install
> autopkgtest [12:19:58]: test dkms-autopkgtest

That dependency problem should resolve automatically once src:linux gets 
decrufted.
But we should probably have a better way to enumerate "all 
linux-header-* packages" in dkms-autopkgtest ... and skip cruft ...

Will think about it post-holidays ...

Andreas

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

#320071

On 12/05/2022 14.21, Andreas Beckmann wrote:
> That dependency problem should resolve automatically once src:linux gets 
> decrufted.
> But we should probably have a better way to enumerate "all 
> linux-header-* packages" in dkms-autopkgtest ... and skip cruft ...

Nope, that is a problem in src:linux-signed-amd64 after src:linux got 
binNMUed, the metapackges are uninstallable

The following packages have unmet dependencies:
  linux-headers-amd64 : Depends: linux-headers-5.17.0-2-amd64 (= 
5.17.6-1) but it is not going to be installed

$ rmadison linux-headers-5.17.0-2-amd64
linux-headers-5.17.0-2-amd64 | 5.17.6-1+b1   | unstable   | amd64


Andreas

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

#320165 — Bug#1010883: marked as done (dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies)

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

Your message dated Thu, 19 May 2022 12:59:03 +0300
with message-id <20220519095903.GA564@localhost>
and subject line Re: Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies
has caused the Debian Bug report #1010883,
regarding dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


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

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

#320482

Control: reopen -1
Control: reassign -1 dkms 3.0.3-1
Control: retitle -1 dkms: autopkgtest mixes headers from sid and testing

> The following packages have unmet dependencies:
>  linux-headers-5.17.0-2-arm64 : Depends: linux-kbuild-5.17 (>= 
> 5.17.6-1) but 5.17.3-1 is to be installed
>  linux-headers-5.17.0-2-cloud-arm64 : Depends: linux-kbuild-5.17 (>= 
> 5.17.6-1) but 5.17.3-1 is to be installed
>  linux-headers-5.17.0-2-rt-arm64 : Depends: linux-kbuild-5.17 (>= 
> 5.17.6-1) but 5.17.3-1 is to be installed

As this still shows up in amd64 and after the latest kernel packages got 
installable again in sid, I have another guess what might be happening 
here [, but I fail to verify that locally -- not any more ;-)].

I'm concentrating on r8168 since that is a more lightweight package than 
the nvidia drivers (but still in non-free)
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r8168/22093828/log.gz

My guess is that apt pinning comes into play here, installing
linux-headers-5.17.0-1-amd64 from testing and
linux-headers-5.17.0-2-amd64 from sid both need linux-kbuild-5.17, but 
the testing version gets selected due to a higher score after pinning, 
but that is not sufficient for the headers from sid.

I tried with the following command line distilled from above log from r8168:

autopkgtest --ignore-restrictions=breaks-testbed  --no-built-binaries 
--apt-upgrade --add-apt-release=unstable 
--pin-packages=unstable=src:dkms --output-dir /tmp/ci-out.$(date +%s) 
r8168 -- schroot autopkgtest-bookworm-amd64

--ignore-restrictions=breaks-testbed on schroot is fine here since 
schroot provides enough isolation for "autopkgtests installing random 
packages"

Unfortunately the pinning does not work here - the full chroot is 
upgraded to unstable first. I'm probably missing some default pinning 
settings here ...

OK, adding --apt-default-release=bookworm makes it work and reproduces 
the error :-) Why is that not needed with the ci chroots?

BTW, /usr/share/autopkgtest/lib/adt_testbed.py run_setup_commands 
(add_apt_releases) has two issues I needed to work around in my chroot:
* it expects /etc/apt/sources.list to exist (I only had 
sources.list.d/bookworm.list)
* it does not cope with tabs instead of spaces as separators

The fix on the dkms side is probably to only select the linux-headers-* 
packages for installation that match the version of the installed 
linux-doc (that's a dependency generated by autodep8). Checking that 
tonight.

Andreas

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

#320483 — Processed: Re: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies

Processing control commands:

> reopen -1
Bug #1010883 {Done: Adrian Bunk <bunk@debian.org>} [src:dkms, src:nvidia-graphics-drivers] dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies
Bug reopened
Ignoring request to alter fixed versions of bug #1010883 to the same values previously set
> reassign -1 dkms 3.0.3-1
Bug #1010883 [src:dkms, src:nvidia-graphics-drivers] dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies
Bug reassigned from package 'src:dkms, src:nvidia-graphics-drivers' to 'dkms'.
No longer marked as found in versions dkms/3.0.3-1 and nvidia-graphics-drivers/470.103.01-3.
Ignoring request to alter fixed versions of bug #1010883 to the same values previously set
Bug #1010883 [dkms] dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies
Marked as found in versions dkms/3.0.3-1.
> retitle -1 dkms: autopkgtest mixes headers from sid and testing
Bug #1010883 [dkms] dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies
Changed Bug title to 'dkms: autopkgtest mixes headers from sid and testing' from 'dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies'.

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

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

#320681

On 27/05/2022 10.59, Paul Gevers wrote:
>> My guess is that apt pinning comes into play here, installing
> 
> That aligns with my suspicion that it's related to the mixing of 
> unstable and testing.

Uploaded a first attempt on the fix. Works for me, let's see how ci.d.o 
likes it. There are probably still corner cases to be handled ...

Andreas

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

#320682 — Bug#1010883: marked as done (dkms: autopkgtest mixes headers from sid and testing)

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

Your message dated Fri, 27 May 2022 14:42:39 +0000
with message-id <E1nubAl-0001Wo-J9@fasolo.debian.org>
and subject line Bug#1010883: fixed in dkms 3.0.3-2
has caused the Debian Bug report #1010883,
regarding dkms: autopkgtest mixes headers from sid and testing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


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

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

#320996 — Processed (with 2 errors): autopkgtest fails

Processing control commands:

> clone -1 -2
Bug #1010883 {Done: Andreas Beckmann <anbe@debian.org>} [dkms] dkms: autopkgtest mixes headers from sid and testing
Bug 1010883 cloned as bug 1012246
> reassign -2 src:nvidia-graphics-drivers-tesla-470
Bug #1012246 {Done: Andreas Beckmann <anbe@debian.org>} [dkms] dkms: autopkgtest mixes headers from sid and testing
Bug reassigned from package 'dkms' to 'src:nvidia-graphics-drivers-tesla-470'.
No longer marked as found in versions dkms/3.0.3-1 and limewire/1.9.1-3.
No longer marked as fixed in versions dkms/3.0.3-2.
> version -2 470.129.06-3
Unknown command or malformed arguments to command.

> tag -1 patch
Bug #1010883 {Done: Andreas Beckmann <anbe@debian.org>} [dkms] dkms: autopkgtest mixes headers from sid and testing
Added tag(s) patch.
> forwarded -1
Unknown command or malformed arguments to command.

> retitle -2 fails on ppc64el due to transitive GPL symbol usage
Bug #1012246 {Done: Andreas Beckmann <anbe@debian.org>} [src:nvidia-graphics-drivers-tesla-470] dkms: autopkgtest mixes headers from sid and testing
Changed Bug title to 'fails on ppc64el due to transitive GPL symbol usage' from 'dkms: autopkgtest mixes headers from sid and testing'.

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

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

#322321 — Processed: Re: nvidia-graphics-drivers-tesla-510: fails on ppc64el due to transitive GPL symbol usage

Processing control commands:

> severity -1 important
Bug #1012246 [src:nvidia-graphics-drivers-tesla-510] nvidia-graphics-drivers-tesla-510: fails on ppc64el due to transitive GPL symbol usage
Severity set to 'important' from 'serious'
> tag -1 - sid bookworm
Bug #1012246 [src:nvidia-graphics-drivers-tesla-510] nvidia-graphics-drivers-tesla-510: fails on ppc64el due to transitive GPL symbol usage
Removed tag(s) sid and bookworm.

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.rc

csiph-web