Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #16539
| From | Simon Josefsson <simon@josefsson.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | python-sigstore / python-tuf: request for packaging help |
| Date | 2024-12-05 23:40 +0100 |
| Message-ID | <JQsFP-e0OD-9@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Hi
I am new to python debian packaging, and I'm looking for guidance and
review my packaging. I'm happy to team-maintain these packages if
someone can add me to the salsa group.
Right now I am working on python-sigstore and my packaging is here:
https://salsa.debian.org/jas/sigstore-python/
as you can see in the pipeline, it currently fails due to lacking tuf:
https://salsa.debian.org/jas/sigstore-python/-/jobs/6706412
It seems python-tuf has an old ITP/RFS report here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934151
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931178
I started from scratch on python-tuf with the latest upstream version,
instead of trying to understand the old packaging work that I couldn't
get to work. Upstream evolved a lot. My packaging is here:
https://salsa.debian.org/jas/python-tuf/
The self-tests tries seems to open some files which fails and I suspect
it is because srcdir != builddir reasons, or something similar, see
errors here:
https://salsa.debian.org/jas/python-tuf/-/jobs/6707693
==================================== ERRORS ====================================
______________ ERROR collecting tests/test_metadata_generation.py ______________
tests/test_metadata_generation.py:10: in <module>
from tests.generated_data.generate_md import generate_all_files
tests/generated_data/generate_md.py:60: in <module>
os.mkdir(OUT_DIR)
E FileNotFoundError: [Errno 2] No such file or directory: 'generated_data/ed25519_metadata'
How is this (seamingly common) problem solved normally? Do we copy test
data files into the build directory somehow? Do we include them in the
package? Do we patch hard-coded paths like this to make it work?
If anyone can review my python-tuf and python-sigstore packages, that
would be appreciated -- all nit-picks and style advice is most
recommended, as I have not worked on python packaging before. Don't
assume I understand any of the debian/* content so feel free to question
some decision.
If you want to build python-tuf locally, it depends on a more recent
version of python3-securesystemslib and you can find it here:
https://salsa.debian.org/jas/securesystemslib/
https://salsa.debian.org/jas/securesystemslib/-/pipelines/774721
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089125
Thanks,
/Simon
Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar
python-sigstore / python-tuf: request for packaging help Simon Josefsson <simon@josefsson.org> - 2024-12-05 23:40 +0100
Re: python-sigstore / python-tuf: request for packaging help Andrey Rakhmatullin <wrar@debian.org> - 2024-12-06 08:40 +0100
Re: python-sigstore / python-tuf: request for packaging help Simon Josefsson <simon@josefsson.org> - 2024-12-06 17:00 +0100
Re: python-sigstore / python-tuf: request for packaging help Andrey Rakhmatullin <wrar@debian.org> - 2024-12-06 17:20 +0100
csiph-web