Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: unblock
X-Debbugs-Cc: [email protected]

Please unblock package pytorch{,-cuda}

We need CUDA >= 12.4 to fix the src:pytorch-cuda FTBFS #1105066, which is due to CUDA's gcc support being too old. But being a contrib package with non-free dependencies, we have to bump the revision and manually rebuild the binaries for all architectures and upload. Anbe plans to make CUDA 12.4 into trixie so I presume CUDA 12.4 will enter testing soon. src:pytorch is the CPU version which has nothing to do with this CUDA transition. But since src:pytorch (main) and src:pytorch-cuda (contrib) is completely identical source package, I need to do the no-change upload of src:pytorch to avoid the weird situation where pytorch is 2.6.0+dfsg-7 while pytorch-cuda is 2.6.0+dfsg-8.
[ Reason ]
Manual rebuild of src:pytorch-cuda against a reasonable CUDA version. The CPU version src:pytorch is no-change manual re-upload to sync the debian revision number with src:pytorch-cuda to avoid messing up.

[ Impact ]
This is a nearly no-risk manual binary rebuild due to the annoyances of non-free dependency.

[ Tests ]
It should work. If there is regression, it's probably a trouble in CUDA.

[ Risks ]
Very small no code change manual rebuild of this package.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ DebDiff ] The only change needed is to mandate the use of the latest CUDA, and avoid the sbuild from picking up the old CUDA version (12.3). diff --git a/debian/control.cuda b/debian/control.cuda index e47874fb..3d0c9077 100644 --- a/debian/control.cuda +++ b/debian/control.cuda @@ -57,7 +57,7 @@ Build-Depends: cmake, python3-setuptools, python3-yaml, patchelf, - nvidia-cuda-toolkit, + nvidia-cuda-toolkit (>= 12.4.0~), nvidia-cuda-toolkit-gcc, nvidia-cudnn (>= 8.7.0.84~cuda11.8), libcudnn-frontend-dev (>= 0.9.2~),
unblock pytorch{,-cuda}/2.6.0+dfsg-8
Thank you for using reportbug

Reply via email to