Control: affects -1 depthcharge-tools Ciao ema,
Emanuele Rocca <e...@debian.org> (2024-08-20): > Package: python3-pkg-resources > Version: 72.2.0-1 > Severity: serious > X-Debbugs-CC: debian-boot@lists.debian.org > > [debian-boot added to CC as this issue breaks d-i builds] Thanks for the heads-up, much appreciated. > Importing pkg_resources fails with the following error: > > (sid-amd64-sbuild)ema@ariel:~$ python3 > Python 3.12.5 (main, Aug 7 2024, 13:49:14) [GCC 14.2.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > >>> import pkg_resources > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 95, > in <module> > import packaging.specifiers > ModuleNotFoundError: No module named 'packaging' > > This is a regression in version 72.2.0-1, whereas 70.3.0-2 worked fine. > > For an example of d-i build failure caused by this problem, see: > https://salsa.debian.org/installer-team/debian-installer/-/jobs/6155545 > > It seems that installing python3-packaging, python3-jaraco.text, and > python3-platformdirs fixes it. I couldn't replicate the FTBFS within a devel sid chroot that has tons of extra packages, including python3-packaging, and python3-platformdirs, but not python3-jaraco.text. Purging python3-platformdirs still gives me a successful build. And from the error/call site quoted above, it seems python3-packaging could be sufficient? (It doesn't list anything but python3:any in Depends or Recommends…) I haven't tried just adding python3-packaging under sbuild though, I'm merely a little curious why the two other packages would be necessary. Cheers, -- Cyril Brulebois (k...@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
