Bug#1094326: pytorch-cuda: rebuild for libbenchmark transition required

From	"M. Zhou" <lumin@debian.org>
Newsgroups	linux.debian.bugs.rc
Subject	Bug#1094326: pytorch-cuda: rebuild for libbenchmark transition required
Date	2025-02-07 01:30 +0100
Message-ID	<KdkpP-eXFm-1@gated-at.bofh.it> (permalink)
References	<K9svE-cdei-3@gated-at.bofh.it> <K9svE-cdei-3@gated-at.bofh.it> <KdhrX-eVSn-1@gated-at.bofh.it> <K9svE-cdei-3@gated-at.bofh.it> <KdhrX-eVSn-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Fri, 2025-02-07 at 02:10 +0500, Andrey Rakhmatullin wrote:
> On Mon, Jan 27, 2025 at 09:15:06AM +0100, Sebastian Ramacher wrote:
> > Source: pytorch-cuda
> > Version: 2.5.1+dfsg-4
> > Severity: serious
> > X-Debbugs-Cc: sramacher@debian.org
> > 
> > pytorch-cuda is involved in the currently ongoing libbenchmark
> > transition and cannot be built on the buildds. Please rebuild all
> > archiectures against libbenchmark1.9.1.
> 
> And for the numpy2 transition now too.
> 
And for the pytorch transition itself too. We will wait until the
pytorch 2.6.0 lands onto unstable before we rebuild pytorch-cuda 2.6.0.
Before that happens, feel free to rip pytorch-cuda off testing if it blocks.

Manually rebuilding this package at the current version for three architectures
manually for 2.5.1 will be a huge waste of human time. It is already broken
with python 3.13 anyway, won't migrate even if rebuilt.

Back to linux.debian.bugs.rc | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Bug#1094326: pytorch-cuda: rebuild for libbenchmark transition required Sebastian Ramacher <sramacher@debian.org> - 2025-01-27 09:20 +0100
  Bug#1094326: pytorch-cuda: rebuild for libbenchmark transition required Andrey Rakhmatullin <wrar@debian.org> - 2025-02-06 22:20 +0100
    Bug#1094326: pytorch-cuda: rebuild for libbenchmark transition required "M. Zhou" <lumin@debian.org> - 2025-02-07 01:30 +0100

csiph-web