On 20/02/2025 06:30, Shengqi Chen wrote:
Hi Emilio,
2025年2月19日 15:40，Emilio Pozuelo Monfort <po...@debian.org> 写道：
Scheduled now.
They are all good now. Thanks!
I still have some questions, since this is my first time to do a
transition independently:
For onednn and xnnpack, the newly built packages are shown as
“unknown” state in the tracker. I suspect it is due to old SONAME
being a prefix of the new one (libdnnl3{,.6}, similar for xnnpack).
Maybe the automatic ben file generator can detect this and handle
the situation, or may be just add a pair of ^$ to the regex?
Yes, the issue is that the new library is a superset of the old, with a "."
separator, which matches \b (word boundary). We could solve that using a manual
tracker, but that's manual work, so let's just assume it's all fine.
And for pytorch, its migration depends on the autopkgtest of
pytorch-{scatter,sparse}. But seems britney does not run tests for
binNMU versions (#944458), so the results on the tracker page are
all failure. Do we need any human intervention on this?
Britney schedules the pytorch tests against rdeps in testing, to ensure they
don't break, as pytorch could migrate before and independently of its rdeps. If
the tests break that way, and it's a test-only thing, we could ignore it. If the
rdeps actually break, then perhaps pytorch should gain Breaks against the old
rdep versions. Then the autopkgtests will be scheduled properly.
Cheers,
Emilio
