guix: gnutls-3.6.12 build failures when using --bootstrap --no-substitutes #21203

1. 
   dongcarl commented at 9:14 pm on February 16, 2021: member

   Corresponding Guix Issue: https://issues.guix.gnu.org/44559

   When supplying --bootstrap --no-substitutes and performing Guix builds with Guix v1.2.0, a build of /gnu/store/vhphki5sg9xkdhh2pbc8gi6vhpfzryf0-gnutls-3.6.12.drv will be attempted. The tests for this build will fail if your system clock is after 2020-10-24 as the certificates included in GnuTLS expires on that date (GnuTLS ticket).

   Although this has been fixed in Guix master some time ago, I believe a --bootstrap --no-substitutes guix pull will attempt to bootstrap the current Guix generation first (which means it will have to build the broken gnutls) before updating to a new generation.

   Currently, there is a workaround for this which involves stopping NTP and manually setting the time prior to the certificate expiry.

   I have posted on the corresponding Guix issues about this asking about alternative solutions to this. Will keep this thread posted on relevant updates.

2. dongcarl assigned dongcarl on Feb 16, 2021
3. 
   dongcarl commented at 0:14 am on February 20, 2021: member

   Some updates here: https://issues.guix.gnu.org/44559#8

   Guix maintainer has indicated that he thinks it would be a good idea to release Guix v1.2.1 with this “hotfix”.

   I’m also pushing for more powerful package transformation options here so that we can sidestep spurious test problems in the future.

   Thank you sipa and achow101 for testing my various solutions to this. I will get it sorted!

4. dongcarl added this to the "Issues" column in a project

   ---

5. 
   dongcarl commented at 4:51 pm on March 23, 2021: member

   Release v1.2.1 is tentatively scheduled for April 18th. More info:

   1. https://lists.gnu.org/archive/html/guix-devel/2021-03/msg00363.html
   2. https://debbugs.gnu.org/cgi/bugreport.cgi?bug=47297
6. 
   Sjors commented at 9:37 am on May 14, 2021: member

   I guess they skipped to 1.3.0?
7. 
   dongcarl commented at 8:28 pm on May 14, 2021: member

   I guess they skipped to 1.3.0?

   Yes! (And this particular issue’s solution is included in v1.3.0)

   I think I’ll just close this for now, as it’ll be mentioned in the README.

8. dongcarl closed this on May 14, 2021

   ---

9. dongcarl moved this from the "Issues" to the "Done" column in a project

   ---

10. DrahtBot locked this on Aug 18, 2022

Contributors
dongcarl Sjors