Public bug reported:
These packages are available in Stonking.
[ Impact ]
* These packages are available in Stonking, but a lot of users will stay on
Resolute for a while.
* This SRU involves the following packages:
cccl-13-3
cuda-crt-13-3
cuda-ctadvisor-13-3
cuda-cudart-13-3
cuda-culibos-13-3
cuda-cuobjdump-13-3
cuda-cupti-13-3
cuda-cuxxfilt-13-3
cuda-documentation-13-3
cuda-gdb-13-3
cuda-meta-13-3
cuda-nvcc-13-3
cuda-nvdisasm-13-3
cuda-nvml-dev-13-3
cuda-nvprune-13-3
cuda-nvrtc-13-3
cuda-nvtx-13-3
cuda-opencl-13-3
cuda-profiler-api-13-3
cuda-sandbox-dev-13-3
cuda-sanitizer-api-13-3
cuda-tileiras-13-3
libcublas-13-3
libcudla-13-3
libcufft-13-3
libcufile-13-3
libcuobjclient-13-3
libcurand-13-3
libcusolver-13-3
libcusparse-13-3
libnpp-13-3
libnvfatbin-13-3
libnvjitlink-13-3
libnvjpeg-13-3
libnvptxcompiler-13-3
libnvvm-13-3
nsight-compute-13-3
nsight-systems-13-3
[ Test Plan ]
* We don't expect problems because
* There are no packages that rely on these
* These packages have no break/replace against existing packages
* Hence our test plan is simply to install the cuda-toolkit-13-3 meta, see
that it installs correctly and if it can run the cuda samples.
[ Where problems could occur ]
* No problem will occur as long as we run the test plan correctly.
[ Other Info ]
* One package can be considered in violation with the SRU policy.
cuda-meta-13-3 ships 3 metas:
* cuda-toolkit-13-3
* cuda-toolkit-13
* cuda-toolkit
These are meant to allow user to user pin himself to a given minor version of
CUDA, or to a major version, or not pin himself at all. You can see in NVIDIA's
own documentation [0] that nvidia enforces the minor version pinning.
In the context of this SRU, cuda-toolkit-13 and cuda-toolkit will have higher
versions than eponymous binary packages from the cuda-meta-13-1 or
cuda-meta-13-2 source package, that is already released. So, if users installed
one of these in the past, they will be migrated to cuda-13-3. This should not
cause issue because
* 13-3 does not drop hardware support compared to 13-1 or 13-2
* 13-3 is officially supported by NVIDIA on Resolute as opposed to 13-1 and
13-2
* The cuda-toolkit-13-1 and cuda-toolkit-13-2 meta is left unchanged.
The other solution would be to drop these 2 binary packages from this
SRU. In this situation, users installing cuda-toolkit-13 on Resolute
will still receive 13-1, which can be considered surprising/annoying
considering the pinning mechanism I explained. This is why I favored
keeping them.
[0] https://developer.nvidia.com/cuda-
downloads?target_os=Linux&target_arch=x86_64&Distribution=Ubuntu&target_version=26.04&target_type=deb_network
** Affects: cuda-meta-13-3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2169604
Title:
Release CUDA 13-3 on Resolute
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cuda-meta-13-3/+bug/2169604/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
