-
Notifications
You must be signed in to change notification settings - Fork 38.8k
Closed
Labels
Description
Is there an existing issue for this?
- I have searched the existing issues
Current behaviour
While doing a mingw guix build on a clean image, osslsigncode fails to build with error
\note: keeping build directory `/tmp/guix-build-osslsigncode-2.5.drv-0'
builder for `/gnu/store/7sm633fs4y8n6cgd9lnqkc19ccrbkxr4-osslsigncode-2.5.drv' failed with exit code 1
build of /gnu/store/7sm633fs4y8n6cgd9lnqkc19ccrbkxr4-osslsigncode-2.5.drv failed
View build log at '/var/log/guix/drvs/7s/m633fs4y8n6cgd9lnqkc19ccrbkxr4-osslsigncode-2.5.drv.gz'.
note: keeping build directory `/tmp/guix-build-gcc-13.3.0.tar.xz.drv-0'
note: keeping build directory `/tmp/guix-build-binutils-2.38.tar.xz.drv-0'
guix shell: error: build of `/gnu/store/7sm633fs4y8n6cgd9lnqkc19ccrbkxr4-osslsigncode-2.5.drv' failed
Looking at the logs, you can see that the error is produced by a failed test due to expired cert
Error: Expired CA certificate:
Signer #0:
Subject: /C=PL/O=osslsigncode/OU=Certification Authority/CN=Intermediate CA
Issuer : /C=PL/O=osslsigncode/OU=Certification Authority/CN=Root CA
Serial : 50F083176D60DACA4AEF9E7B1D9521A92C4196D3
Certificate expiration date:
notBefore : Jan 1 00:00:00 2018 GMT
notAfter : Jan 1 00:00:00 2026 GMT
X509_verify_cert: certificate verify error: certificate has expired
Signature CRL verification: failed
Signature verification: failed
Faking the time to 2025 before the container preparation and then doing a normal build with the right time works normally.
Expected behaviour
Ideally there should be no timebombs creating guix environments
Steps to reproduce
Try a guix build from a recently created container, updating the whole time-machine
Relevant log output
No response
How did you obtain Bitcoin Core
Compiled from source
What version of Bitcoin Core are you using?
v30.1
Operating system and version
Fedora 43
Machine specifications
No response
delta1, tomt1664 and danielabrozzoni