Bug#1094440: transition: xnnpack and onednn for PyTorch 2.6

[Chen Shengqi <harry@debian.org>]

Hi,

> -----Original Message-----
> From: Emilio Pozuelo Monfort <pochu27@gmail.com>
> Sent: Monday, February 17, 2025 10:22 PM
> >
> > For pytorch{,-cuda}:
> >
> > * pytorch-{cluster,scatter,vision,ignite}, baler: builds without issue
> > * pytorch-sparse: failed, in testing, @lumin is looking into it
> > * skorch, pytorch-{audio, geometric}, python-array-api-compat: failed, but
> > not in testing

Here are some updates:

All aforementioned rdeps EXCEPT the following:
 pytorch-{audio,geometric}, python-array-api-compat
Could build against new pytorch.

Just a double-check - I still see pytorch-{cluster,scatter,sparse} shown
as "bad" on the transition tracker. Are their binNMUs scheduled?

Thanks,
Shengqi Chen