[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1003173: marked as done (bullseye-pu: package nvidia-cuda-toolkit/11.2.2-3+deb11u1)

Your message dated Sat, 26 Mar 2022 11:59:13 +0000
with message-id <c4d20274f6d76a43fb574d2177f6e3af4235e4be.camel@adam-barratt.org.uk>
and subject line Closing p-u requests for updates in 11.3
has caused the Debian Bug report #1003173,
regarding bullseye-pu: package nvidia-cuda-toolkit/11.2.2-3+deb11u1
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.)


-- 
1003173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003173
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian.org@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

Attachment: nct-11.2.2-3+deb11u1.diff.xz
Description: application/xz

Attachment: nvidia-cuda-toolkit_11.2.2-3+deb11u1_amd64.changes.bindiff.xz
Description: application/xz


--- End Message ---
--- Begin Message --- 
Package: release.debian.org
Version: 11.3

Hi,

The updates referenced by these bugs were included in stable as part of
this morning's 11.3 point release.

Regards,

Adam

--- End Message ---
Reply to: