unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 46829@debbugs.gnu.org
Subject: bug#46829: Fresh install of 1.2.0 can't guix pull
Date: Mon, 12 Apr 2021 14:25:11 +0200	[thread overview]
Message-ID: <87zgy3pu54.fsf@gnu.org> (raw)
In-Reply-To: <YHQFDOGNyqVlmWm0@jasmine.lan> (Leo Famulari's message of "Mon, 12 Apr 2021 04:30:04 -0400")

Hi Leo,

Leo Famulari <leo@famulari.name> skribis:

> I couldn't figure out how to test an update of the Guix package, but
> here is my patch updating le-certs.

Cool!

> `make update-guix-package` segfaults for me, sometime after it updates
> the source tree but before adding the source checkout to the store.

Could you grab a backtrace, with:

  gdb $(which guile) core

where ‘core’ is the core file (it might live elsewhere on a foreign
distro).  It could be that the foreign distro packages being used are
buggy, or that a mixture of Guix- and distro-provided libraries are
being loaded.

In the meantime, you could also update the ‘guix’ package by hand for
testing purposes.

> From f0da45e7b78a6dd2b51dec1a948ea95866811c02 Mon Sep 17 00:00:00 2001
> From: Leo Famulari <leo@famulari.name>
> Date: Mon, 12 Apr 2021 02:19:33 -0400
> Subject: [PATCH] gnu: le-certs: Update to new Let's Encrypt certificates.
>
> * gnu/packages/certs.scm (le-certs): Update the certificate store.
> [inputs]: Add isrgrootx2.pem, letsencryptauthorityr3.pem,
> letsencryptauthorityr4.pem, letsencryptauthoritye1.pem, and
> letsencryptauthoritye2.pem. Remove letsencryptauthorityx3.pem and
> letsencryptauthorityx4.pem.
> [arguments]: Adjust the builder accordingly.

Nice!  So how do we know if/when this has to be updated?  Maybe we can
add a ‘release-monitoring-url’ property?

I just checked that the files currently in use were still there, and
they are, but they’re outdated.

Thanks!

Ludo’.




  reply	other threads:[~2021-04-12 12:26 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-28 10:27 bug#46829: Fresh install of 1.2.0 can't guix pull Christopher Baines
2021-02-28 11:06 ` Andreas Enge
2021-02-28 11:10 ` Andreas Enge
2021-03-01 10:15   ` Ludovic Courtès
2021-03-01  9:49 ` zimoun
2021-03-05 10:49   ` Christopher Baines
2021-03-01 10:19 ` Ludovic Courtès
2021-03-01 12:03   ` Andreas Enge
2021-03-17 14:36   ` Ludovic Courtès
2021-04-11 20:41     ` Leo Famulari
2021-04-12  1:29       ` Leo Famulari
2021-04-12  6:42         ` Leo Famulari
2021-04-12  8:30           ` Leo Famulari
2021-04-12 12:25             ` Ludovic Courtès [this message]
2021-04-12 17:15               ` Leo Famulari
2021-04-12 17:32                 ` Leo Famulari
2021-04-13  8:12                   ` Ludovic Courtès
2021-04-13 18:09                     ` Leo Famulari
2021-04-21 13:14                       ` Ludovic Courtès
2021-04-12 12:25             ` Ludovic Courtès
2021-04-12 17:02               ` Leo Famulari
2021-04-12 18:26                 ` Leo Famulari
2021-04-13 17:47                   ` Leo Famulari
2021-04-13  9:29           ` bug#46829: `guix pull` uses incorrect certificate store Ludovic Courtès
2021-04-13 17:44             ` Leo Famulari
2021-04-14 10:50               ` Ludovic Courtès
2021-04-14 19:57                 ` Maxime Devos
2021-05-31 19:17                 ` Leo Famulari
2021-04-10 19:02 ` bug#46829: Fresh install of 1.2.0 can't guix pull Leo Famulari
2021-04-10 19:45   ` Christopher Baines
2021-04-10 20:30     ` Leo Famulari
2021-04-10 21:09       ` Leo Famulari
2021-04-10 21:21         ` Christopher Baines
2021-04-10 22:54           ` Leo Famulari
2021-04-10 23:04 ` Leo Famulari
2021-04-10 23:13 ` Leo Famulari
2021-04-14  1:08 ` Leo Famulari
2021-04-14  9:44   ` François

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zgy3pu54.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=46829@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).