Your message dated Thu, 15 Feb 2024 13:17:27 +0100 with message-id <98a2b0d4-63a1-743c-3081-5e406c34b...@debian.org> and subject line Re: nvidia-cuda-samples: autopkgtest needs update for new version of linux has caused the Debian Bug report #1063364, regarding nvidia-cuda-samples: autopkgtest needs update for new version of linux 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 ow...@bugs.debian.org immediately.) -- 1063364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: nvidia-cuda-samples Version: 12.1~dfsg-1 Severity: serious X-Debbugs-CC: li...@packages.debian.org Tags: sid trixie User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:linux Dear maintainer(s),With a recent upload of linux the autopkgtest of nvidia-cuda-samples fails in testing when that autopkgtest is run with the binary packages of linux from unstable. It passes when run with only packages from testing. In tabular form:pass fail linux from testing 6.6.15-2 nvidia-cuda-samples from testing 12.1~dfsg-1 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 linux to testing [1]. Of course, linux shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in linux was intended and your package needs to update to the new situation.If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from linux should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests.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=linux https://ci.debian.net/data/autopkgtest/testing/amd64/n/nvidia-cuda-samples/42760273/log.gz 1664s I: Testing binary package nvidia-fs-dkms1664s I: Trying to install build dependency nvidia-current/525.147.05 for 6.6.15-amd641664s Sign command: /lib/modules/6.6.15-amd64/build/scripts/sign-file 1664s Signing key: /var/lib/dkms/mok.key 1664s Public certificate (MOK): /var/lib/dkms/mok.pub1664s Certificate or key are missing, generating self signed certificate for MOK... 1664s Creating symlink /var/lib/dkms/nvidia-current/525.147.05/source -> /usr/src/nvidia-current-525.147.051664s 1664s Building module: 1665s Cleaning build area...1686s env NV_VERBOSE=1 make -j64 modules KERNEL_UNAME=6.6.15-amd64..........(bad exit status: 2) 1686s Error! Bad return status for module build on kernel: 6.6.15-amd64 (x86_64) 1686s Consult /var/lib/dkms/nvidia-current/525.147.05/build/make.log for more information.1686s autopkgtest [06:12:31]: test dkms-autopkgtest-nvidia-fsOpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---On Tue, 6 Feb 2024 21:31:44 +0100 Paul Gevers <elb...@debian.org> wrote:KERNEL_UNAME=6.6.15-amd64..........(bad exit status: 2)1686s Error! Bad return status for module build on kernel: 6.6.15-amd64 (x86_64)That was #1063363 in nvidia-kernel-dkms. Andreas
--- End Message ---