Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies
On 27/05/2022 16.22, Andreas Beckmann wrote: > 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 ... Looks not too bad. Current problems: lime-forensics: used dkms-autopkgtest manually, not via Testsuite: autopkgtest-pkg-dkms merge-request !2 (only autopkgtest buggy, module builds fine) r8125: bug #1012014 - r8125: fails to build module for Linux 5.17 (new upstream release available) nvidia-graphics-drivers-tesla-470: fails on ppc64el due to transitive GPL symbol usage, reported upstream nvidia-graphics-drivers-tesla-510: improved version in experimental, but has the same problem on ppc64el as 470 (not yet in sid due to moving a package from nvidia-graphics-drivers to -tesla-510) feel free to temporarily remove from testing Since these bugs (modules failing to build) are already present in testing and only exposed by the new dkms by making the autopkgtest run no longer a no-op, perhaps you could just ignore the failing tests and hint dkms into testing? (-tesla-510 would need some forced hint for reintroduction into testing as well, since I don't think an upstream fix for ppc64el will be available in time when I move nvidia-graphics-drivers from 470 to 510 as default in sid) Andreas
Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies
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
Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies
Hi Andreas, On 26-05-2022 10:58, Andreas Beckmann wrote: Control: reopen -1 Control: reassign -1 dkms 3.0.3-1 Control: retitle -1 dkms: autopkgtest mixes headers from sid and testing Thanks. I agree with this action. 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. OK, adding --apt-default-release=bookworm makes it work and reproduces the error :-) Why is that not needed with the ci chroots? I *suspect* that's because ci.d.o and salsa.d.o don't use chroots but lxc. (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) That may be a bug in the autopkgtest chroot backend. Nearly all my experience is with the lxc backend, so it would need investigation. * it does not cope with tabs instead of spaces as separators Same, feel free to report the bug. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies
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
Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies
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
Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies
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
Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies
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...@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: passfail dkmsfrom testing3.0.3-1 nvidia-graphics-drivers from testing470.103.01-3 all others from testingfrom 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
