On Thu Apr 9, 2026 at 8:38 PM BST, Jeroen Ploemen wrote: Hi Jeroen,
> I took a look at the beets package, up for sponsorship in the Python
> team:
Thanks for your time! Again ;-)
> * repo: upstream and pristine-tar branches are stale. Try 'gbp push'.
> * control: most version requirements in both build-depends and the
> dependencies of the binary package are ancient (as in, already met
> in oldstable), please remove the outdated constraints.
> * control: missing field 'Built-Using: ${sphinxdoc:Built-Using}' on
> the documentation pkg (please ignore lintian if it complains about
> adding such a field on an architecture-independent package, known
> bug).
> * control: the pkg is missing a hard dependency on python3-pil for the
> unconditional imports in beets/util/artresizer.py (currently only a
> suggest).
All these are done.
Additionally, I saw some of the BPD tests failed again in the i386 build step.
I feel I'm continually trying to patch these up, disabling them, checking if
the patch is still needed, enabling them again, and so on.
It seems pointless to resist: upstream doesn't support py 3.14 yet.
So I've disabled tests on py 3.14 at module level now when I get errors on py
3.14 but not on 3.13.
> Once the above comments have been addressed, simply re-add the
> package to the IRC channel topic and/or ping me by e-mail.
I see salsa pipelines seem to be in trouble. Package builds fine in sbuild
locally here.
Br,
Pieter
signature.asc
Description: PGP signature
