unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: wolf <wolf@wolfsden.cz>
To: 63596@debbugs.gnu.org
Subject: bug#63596: guix-git-authenticate fails on fresh git clone
Date: Fri, 19 May 2023 23:41:59 +0200	[thread overview]
Message-ID: <ZGftJ44ETe5sVZva@ws> (raw)

[-- Attachment #1: Type: text/plain, Size: 1928 bytes --]

Hello,

as instructed on the Building from Git documentation page, I am writing
regarding a failing test (guix-git-authenticate) on a fresh git clone of guix
repository.  I am unsure what the exact commit was (sorry!), but I'm pretty sure
it is not relevant in this case (assuming it was not fixed this week).

    $ cat tests/guix-git-authenticate.log
    + '[' -d /home/wolf/sources/guix/.git ]
    + guile -c '(use-modules (git))
      (member "refs/heads/keyring" (branch-list (repository-open ".")))'
    + intro_commit=9edb3f66fd807b096b48283debdcddccfea34bad
    + intro_signer='BBB0 2DDF 2CEA F6A8 0D1D  E643 A2A0 6DF2 A33A 54FA'
    + cache_key=test-3776
    + guix git authenticate 9edb3f66fd807b096b48283debdcddccfea34bad 'BBB0 2DDF 2CEA F6A8 0D1D  E643 A2A0 6DF2 A33A 54FA' '--cache-key=test-3776' --stats
    +'--end=9549f0283a78fe36f2d4ff2a04ef8ad6b0c02604'
    guix git: error: Git error: cannot locate remote-tracking branch 'keyring'
    + v1_2_0_commit=a099685659b4bfa6b3218f84953cbb7ff9e88063
    + guix git authenticate 9edb3f66fd807b096b48283debdcddccfea34bad 'BBB0 2DDF 2CEA F6A8 0D1D  E643 A2A0 6DF2 A33A 54FA' '--cache-key=test-3776' --stats
    +'--end=a099685659b4bfa6b3218f84953cbb7ff9e88063'
    guix git: error: Git error: cannot locate remote-tracking branch 'keyring'
    FAIL tests/guix-git-authenticate.sh (exit status: 1)

As you can see, it complains about branch `keyring' being missing.  Indeed, once
I created it:

    $ g co keyring
    branch 'keyring' set up to track 'origin/keyring'.
    Switched to a new branch 'keyring'

After this the test passed just fine.  I did not have time to look into it more
in depth nor produce a patch, so I thought I will at least report it, as
instructed by the documentation.

Have a nice day,
W.

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2023-05-19 21:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-19 21:41 wolf [this message]
2023-05-20 15:16 ` bug#63596: guix-git-authenticate fails on fresh git clone Graham Addis

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=ZGftJ44ETe5sVZva@ws \
    --to=wolf@wolfsden.cz \
    --cc=63596@debbugs.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 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).