Package: release.debian.org Severity: normal Tags: bullseye User: release.debian....@packages.debian.org Usertags: pu
Hi, I'd like to update nvidia-cuda-toolkit in bullseye/non-free in order to disable the non-functional python3 support in cuda-gdb. This causes segmentation faults if libpython2.7.so.1 is available on the system, due to dlopening that library even if we built cuda-gdb against python3.x. (python3 support in cuda-gdb became functional and was re-enabled in 11.4, it does not look fixable in 11.2 due to incomplete python3 support) I'll take this opportunity to also update the bundled openjdk-8 snapshot to the version currently in unstable, probably fixing a ton of CVEs. Upstream treats the cuda toolkit as a bundle of several individually versioned components, unfortunately the versions are not always monotonic... In order to detect (and workaround) the versioning errors at buildtime (and not by ftp-master rejecting the binary packages), I've automated that in debian/rules. That change may look big, but to show that it does not affect the resulting binary packages I'm also attaching a binary debdiff against a rebuild of 11.2.2-3 as 11.2.2-3+deb11u1 with no further changes than the version bump. Andreas
nct-11.2.2-3+deb11u1.diff.xz
Description: application/xz
nvidia-cuda-toolkit_11.2.2-3+deb11u1_amd64.changes.bindiff.xz
Description: application/xz
