Control: retitle -1 unblock: pytorch-cuda/2.6.0+dfsg-7+b1 The ROM for ppc64el binary has been filed at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107961
On Tue, 2025-06-17 at 23:29 -0400, M. Zhou wrote: > retitle -1 unblock: pytorch-cuda/2.6.0+dfsg-7+b1 > > I have manually binNMU'ed the pytorch-cuda package: > $ rmadison python3-torch-cuda > > python3-torch-cuda | 2.6.0+dfsg-7 | testing/contrib | ppc64el > python3-torch-cuda | 2.6.0+dfsg-7 | unstable/contrib | ppc64el > python3-torch-cuda | 2.6.0+dfsg-7+b1 | testing/contrib | amd64, > arm64 > python3-torch-cuda | 2.6.0+dfsg-7+b1 | unstable/contrib | amd64, > arm64 > > It seems that the +b1 version already migrated. Is it really necessary to file > the unblock? BTW, since binNMU works, src:pytorch (CPU-only) can be left > intact. > > And can we remove the ppc64el architecture for src:pytorch-cuda from testing? > The libcuda1 dependency is no longer available on ppc64el, so pytorch-cuda > is not installable anyway. > > On Sat, 2025-06-14 at 08:59 +0200, Sebastian Ramacher wrote: > > On 2025-06-13 16:28:38 -0400, M. Zhou wrote: > > > > No, you can also upload maintainer-built rebuilds. If there is no source > > change at all and only a rebuild, this would be preferred. But please do > > not forget to file an unblock request for the rebuilds as they also will > > not migrate automatically. > > > > Cheers
