Skip to content
This repository has been archived by the owner on Oct 16, 2024. It is now read-only.

tests fail after 2024-06-12 #116

Closed
bmwiedemann opened this issue Jan 29, 2023 · 5 comments
Closed

tests fail after 2024-06-12 #116

bmwiedemann opened this issue Jan 29, 2023 · 5 comments

Comments

@bmwiedemann
Copy link

While working on reproducible builds for openSUSE, I found that
our bmap-tools-3.6 package fails to build after 2024-06-12.

To reproduce, you could set the system clock or use the following on Debian or openSUSE:

osc co openSUSE:Factory/bmap-tools && cd $_
osc build --clean --vm-type=kvm --noservice --build-opt=--vm-custom-opt="-rtc base=2024-06-13T00:00:00" standard

actual results:

tests/test_CLI.py::TestCLI::test_valid_signature FAILED
...

----------------------------- Captured stderr call -----------------------------
bmaptool: �[91mERROR�[0m: An error occurred, here is the traceback:
Traceback (most recent call last):
   File "/home/abuild/rpmbuild/BUILDROOT/bmap-tools-3.6-0.x86_64/usr/lib/python3.8/site-packages/bmaptools/CLI.py", line 205, in verify_detached_bmap_signature
    sigs = context.verify(signed_data, signature, None)[1].signatures
  File "/usr/lib64/python3.8/site-packages/gpg/core.py", line 558, in verify
    raise errors.BadSignatures(results[1], results=results)

bmaptool: �[91mERROR�[0m: discovered a BAD GPG signature: tests/test-data/signatures/test.image.bmap.v2.0.valid-sig

This is likely due to some expiring gpg key.
@Abooksks
Copy link

tests/test_CLI.py::TestCLI::test_valid_signature FAILED
...

----------------------------- Captured stderr call -----------------------------
bmaptool: �[91mERROR�[0m: An error occurred, here is the traceback:
Traceback (most recent call last):
File "/home/abuild/rpmbuild/BUILDROOT/bmap-tools-3.6-0.x86_64/usr/lib/python3.8/site-packages/bmaptools/CLI.py", line 205, in verify_detached_bmap_signature
sigs = context.verify(signed_data, signature, None)[1].signatures
File "/usr/lib64/python3.8/site-packages/gpg/core.py", line 558, in verify
raise errors.BadSignatures(results[1], results=results)

bmaptool: �[91mERROR�[0m: discovered a BAD GPG signature: tests/test-data/signatures/test.image.bmap.v2.0.valid-sig

@bmwiedemann
Copy link
Author

2024-06-12 is less than 5 months from now. Any plans to avoid failing tests?

@dedekind
Copy link
Contributor

@bmwiedemann hi, this project needs a maintaner, I do not have time for it any longer. I sent this e-mail to Yocto community:

https://lists.yoctoproject.org/g/yocto/message/62256

Feel free to volunteer to do this work for Yocto community.

@dedekind
Copy link
Contributor

dedekind commented Mar 6, 2024

Hello, the project was moved and now owned by a new team. Please, work with them. Check the README.md file. Thanks!

@dedekind dedekind closed this as completed Mar 6, 2024
@bnavigator bnavigator mentioned this issue Mar 8, 2024
Closed
@bnavigator
Copy link 

# extend signing key expiration for reproducible builds
export GNUPGHOME=$PWD/tests/test-data/gnupg
echo "expire
50y
key 1
expire
50y
save" | gpg --command-fd=0 --batch --edit-key 927FF9746434704C5774BE648D49DFB1163BDFB4

jo-so-nx added a commit to jo-so-nx/bmaptool that referenced this issue Mar 9, 2024
@jo-so-nx
tests/CLI: update gpg key
385f4d6 
The gpg expires on 2024-06-12 (see [1]) which makes all tests fail using the
key. Therefore extend the expiration to 50 year as suggested in [2].

[1]: intel#116
[2]: yoctoproject#1 (comment)

Signed-off-by: Jörg Sommer <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@bmwiedemann @dedekind @bnavigator @Abooksks