Re: pytorch is marked for autoremoval from testing
Hi Gard,
Thank you for the attention. I do not have idea on the GCC-11 ftbfs
bugs. But the other bugs should be easy to fix. The Pytorch autopkgtest
failure can be fixed by skipping the corresponding test cases,
as they are irreasonably assuming compilation against MKL.
I'm personally unable to focus on debian as a new first-year phd
student. So any help would be appreciated. I can provide brief pointers
and reviews upon request.
On Mon, 2021-11-01 at 10:07 +0100, Gard Spreemann wrote:
> Hello,
>
> Do we need some coordinated effort to tackle these, or is there some
> trivial fix that just needs to be applied?
>
> -- Gard
>
>
> Debian testing autoremoval watch <noreply@release.debian.org> writes:
>
> > pytorch 1.7.1-7 is marked for autoremoval from testing on 2021-11-
> > 09
> >
> > It is affected by these RC bugs:
> > 984304: pytorch: ftbfs with GCC-11
> > https://bugs.debian.org/984304
> > 994423: pytorch: Baseline violation on armhf
> > https://bugs.debian.org/994423
> >
> > It (build-)depends on packages with these RC bugs:
> > 984190: libnop: ftbfs with GCC-11
> > https://bugs.debian.org/984190
> > 984270: onednn: ftbfs with GCC-11
> > https://bugs.debian.org/984270
> > 997271: xnnpack: FTBFS: intrinsics-polyfill.h:27:6: error:
> > conflicting types for ‘_mm_storeu_si32’; have ‘void(const
> > void *, __m128i)’
> > https://bugs.debian.org/997271
> >
> >
> >
> > This mail is generated by:
> > https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl
> >
> > Autoremoval data is generated by:
> > https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
>
Reply to: