Hello and thank you for these changes. A few remarks - cuda-meta-13-4: we are now allowed to include the `cuda` and `cuda-13-4` metas. Can you uncomment the relevant lines in the debian/control file? I'm not sure a `cuda-13` meta should exists, you can verify that on NVIDIA's own packaging.
- since nsight-compute (and that relevant for others, mostly nsight-systems) repacks the tarball, the version should in theory be `2026.3.1.2+dfsg-0ubuntu1`. However, since we always want users that are installing nvidia's archive to receive the package from nvidia instead of ours, the nvidia's own version being `2026.3.1.2-1`, we cannot do that. I'll reach out on MM to ask how to solve this problem. - again nsight-compute / nsight-systems: `xz`'s tarball can be very slightly different if it run in a single process or in several. We want determinism. See here [0] how we handled this on ubuntu-cuda-packaging- tools. Can you verify if tarball generation is deterministic? A nit: it would be great to have the order of the package consistent between the summary, the list, the files. Maybe alphabetical? I believe the tooling would require an update in that regard. [0] https://git.launchpad.net/ubuntu/+source/ubuntu-cuda-packaging- tools/tree/files/usr/libexec/ubuntu_cuda_get_orig_source?h=ubuntu/stonking#n207 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2169616 Title: [needs-packaging] cuda-13-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2169616/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
