guix git: error: unknown introductory commit and signer

  • Open
  • quality assurance status badge
Details
3 participants
  • Leo Famulari
  • Maxim Cournoyer
  • Rostislav Svoboda
Owner
unassigned
Submitted by
Rostislav Svoboda
Severity
normal

Debbugs page

Rostislav Svoboda wrote 2 weeks ago
CAEtmmexkywgm4G0L9Qga1LxYpm7f_LMSEXVNdds7UdsWKeMW9w@mail.gmail.com
Hello, is the error below caused by this commit?

9c7ef1994d 2025-02-27 .guix-authorizations: Use subkey for
Steve/futurile. (11 minutes ago) Maxim Cournoyer

Cheers,
Bost


$ git pull --rebase savannah master
remote: Counting objects: 23, done.
remote: Compressing objects: 100% (23/23), done.
remote: Total 23 (delta 18), reused 0 (delta 0)
Unpacking objects: 100% (23/23), 6.69 KiB | 427.00 KiB/s, done.
* branch master -> FETCH_HEAD
1fbc2625d2..9c7ef1994d master -> savannah/master
Updating 4270c484ca..9c7ef1994d
Fast-forward
.guix-authorizations | 3 ++-
gnu/packages/golang-crypto.scm | 79
+++++++++++++++++++++++++++++++++++++++++++++----------------------------------
gnu/packages/password-utils.scm | 2 +-
gnu/packages/python-science.scm | 17 ++++-------------
4 files changed, 52 insertions(+), 49 deletions(-)
guix git: error: unknown introductory commit and signer
Leo Famulari wrote 2 weeks ago
(name . Rostislav Svoboda)(address . rostislav.svoboda@gmail.com)
Z8BtLVZeAHUVXqH3@jasmine.lan
On Thu, Feb 27, 2025 at 02:16:47PM +0100, Rostislav Svoboda wrote:
Toggle quote (2 lines)
> Hello, is the error below caused by this commit?

What command did you run to get the error in your email's subject?

Toggle quote (3 lines)
> 9c7ef1994d 2025-02-27 .guix-authorizations: Use subkey for
> Steve/futurile. (11 minutes ago) Maxim Cournoyer

Based on this commit, `guix git authenticate` does succeed for me:

------
$ guix git authenticate
guix git: successfully authenticated commit 9c7ef1994db6c11c95c16891437a5c8ed229eb64
------

And `guix pull` succeeds too.
Rostislav Svoboda wrote 2 weeks ago
(name . Leo Famulari)(address . leo@famulari.name)
CAEtmmezuDzDgg03E0P90Y0G-_xJp4DVyBSVBatRJmr5Mto9hXw@mail.gmail.com
Toggle quote (2 lines)
> What command did you run to get the error in your email's subject?

The command was `git pull --rebase savannah master`. (See my first
email in the thread)

Cheers,
Bost
Leo Famulari wrote 2 weeks ago
(name . Rostislav Svoboda)(address . rostislav.svoboda@gmail.com)
Z8CAdCkKjJ2MK_A3@jasmine.lan
On Thu, Feb 27, 2025 at 02:52:18PM +0100, Rostislav Svoboda wrote:
Toggle quote (3 lines)
> The command was `git pull --rebase savannah master`. (See my first
> email in the thread)

Right.

You might need to check out the 'keyring' branch and pull it in order to
get the updates to the keyring, since Steve (futurile) is a new
committer.

If you'd rather avoid clobbering your regular source checkout, which
would require a full rebuild in order to use './pre-inst-env' again, you
can check out the keyring in a worktree. Something like this:

$ git worktree add /tmp/keyring origin/keyring && cd /tmp/keyring && git pull origin keyring
Maxim Cournoyer wrote 2 weeks ago
(name . Leo Famulari)(address . leo@famulari.name)
87bjunj678.fsf@gmail.com
Hi,

Leo Famulari <leo@famulari.name> writes:

Toggle quote (10 lines)
> On Thu, Feb 27, 2025 at 02:52:18PM +0100, Rostislav Svoboda wrote:
>> The command was `git pull --rebase savannah master`. (See my first
>> email in the thread)
>
> Right.
>
> You might need to check out the 'keyring' branch and pull it in order to
> get the updates to the keyring, since Steve (futurile) is a new
> committer.

Actually with a recent change (a few months?) to Guix, I believe it's
now necessary to run 'guix pull' to get newly authorized keys; I'm not
sure in what commit though.

Could someone confirm or infirm that? With the link to the actual
change as a bonus, if you have that! If confirmed, we should probably
extend our contributing doc to document this new gotcha.

--
Thanks,
Maxim
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 76608@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 76608
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help