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:
cuda-cccl-13-2
cuda-crt-13-2
cuda-ctadvisor-13-2
cuda-cudart-13-2
cuda-culibos-13-2
cuda-cuobjdump-13-2
cuda-cupti-13-2
cuda-cuxxfilt-13-2
cuda-documentation-13-2
cuda-gdb-13-2
cuda-meta-13-2
cuda-nvcc-13-2
cuda-nvdisasm-13-2
cuda-nvml-dev-13-2
cuda-nvprune-13-2
cuda-nvrtc-13-2
cuda-nvtx-13-2
cuda-profiler-api-13-2
cuda-sandbox-dev-13-2
cuda-sanitizer-api-13-2
cuda-tileiras-13-2
libcublas-13-2
libcufft-13-2
libcufile-13-2
libcuobjclient-13-2
libcurand-13-2
libcusolver-13-2
libcusparse-13-2
libnpp-13-2
libnvfatbin-13-2
libnvjitlink-13-2
libnvjpeg-13-2
libnvptxcompiler-13-2
libnvvm-13-2
nsight-compute-13-2
nsight-systems-13-2
cuda-opencl-13-2
cuda-nsight-13-2
libcudla-13-2
[ 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-2 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-2 ships 3 metas:
* cuda-toolkit-13-2
* 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 source package,
that is already released. So, if users installed one of these in the past, they
will be migrated to cuda-13-2. This should not cause issue because
* 13-2 does not drop hardware support compared to 13-1
* 13-1 is not officially supported by NVIDIA on Resolute. 13-2 isn't
either, but is closer to it. 13-3 is the first officially supported one
* The cuda-toolkit-13-1 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=24.04&target_type=deb_network
** Affects: cuda-meta-13-2 (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/2164757
Title:
Release the CUDA-13-2 packages on Resolute
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cuda-meta-13-2/+bug/2164757/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
