all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Roel Janssen <roel@gnu.org>
Cc: 73173@debbugs.gnu.org
Subject: [bug#73173] [PATCH] gnu: Update python-rdflib to 7.0.0.
Date: Mon, 30 Sep 2024 21:47:15 +0200	[thread overview]
Message-ID: <87bk046i0s.fsf@gnu.org> (raw)
In-Reply-To: <a3add093d5dba22f20d977d5a6b3182e3e505255.camel@gnu.org> (Roel Janssen's message of "Sun, 29 Sep 2024 17:51:46 +0200")

Hi,

Roel Janssen <roel@gnu.org> skribis:

> Upon invoking 'git push', I'm receiving this error message:
>   All 109 channel news entries are valid.
>   guix git: error: unknown introductory commit and signer
>   error: failed to push some refs to  
> 'ssh://git.savannah.gnu.org/srv/git/guix.git'
>
> My GPG key is still the same, although I updated the expiration date
> (and updated the key on Savannah). It looks like the key information in
> .guix-authorizations for me is still correct.
>
> Since it's been a while, where should I start reading the documentation
> on understanding/overcoming this problem?

Oh.  The message comes from ‘guix git authenticate’, and it’s admittedly
unclear.

To fix it, you must first manually run:

  guix git authenticate 9edb3f66fd807b096b48283debdcddccfea34bad \
    "BBB0 2DDF 2CEA F6A8 0D1D  E643 A2A0 6DF2 A33A 54FA"

This will record the introductory commit and signer (the two hex strings
above) in ‘.git/config’, and from there you should be all set.

This is only briefly mentioned in
<https://guix.gnu.org/manual/devel/en/html_node/Building-from-Git.html>.

HTH,
Ludo’.




  reply	other threads:[~2024-09-30 19:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10 19:33 [bug#73173] [PATCH] gnu: Update python-rdflib to 7.0.0 Roel Janssen
2024-09-25 16:05 ` Ludovic Courtès
2024-09-29 15:51   ` Roel Janssen
2024-09-30 19:47     ` Ludovic Courtès [this message]
2024-09-30 20:55       ` bug#73173: " Roel Janssen

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

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

  git send-email \
    --in-reply-to=87bk046i0s.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=73173@debbugs.gnu.org \
    --cc=roel@gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.