unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "N. Y." <ningyuan.sg@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: 64059@debbugs.gnu.org
Subject: bug#64059: Sudden unexplained error during guix pull: "channel dependency has an invalid introduction field"
Date: Tue, 20 Jun 2023 01:21:58 +0800	[thread overview]
Message-ID: <CAEavL=UK+yn8dcB0mEZK-4EtpqDk5UCEgL5ujsscSpaTA=UthQ@mail.gmail.com> (raw)
In-Reply-To: <87edm7a4vc.fsf@gmail.com>

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

Hi Simon,

Thanks for taking a look! The keyring branch doesn't seem empty on my end,
though. https://github.com/ning-y/ninguix/tree/keyring

Maybe it looks empty because it is an orphan branch? I always had it as an
orphan branch though (that part never changed) and it had worked before.

On Tue, Jun 20, 2023, 00:36 Simon Tournier <zimon.toutoune@gmail.com> wrote:

> Hi,
>
> On Wed, 14 Jun 2023 at 01:56, "N. Y." <ningyuan.sg@gmail.com> wrote:
>
> > Updating channel 'ninguix' from Git repository at '
> > https://github.com/ning-y/ninguix'...
> >
> /home/ning/.cache/guix/checkouts/y6rzf466if75ebhoqonk2dqs6ac5d75tvkvziqptmqvawztuphda/.guix-channel:10:4:
> > error: channel dependency has an invalid introduction field
>
> [...]
>
> >       (channel
> >         (name 'ninguix)
> >         (url "https://github.com/ning-y/ninguix")
> >         (branch "main")
> >         (introduction
> >           (make-channel-introduction
> >             "3f7eb8b5064445d72649b1b27f714b86f3946a9a"
> >             (openpgp-fingerprint
> >               "4523 A758 035C 5177 7A8F  1E1F 2CB0 E8CD 7035 5FB7"))))
>
> The branch ’keyring’ seems empty, is it expected?  I mean the manual
> reads:
>
>         Additionally, your channel must provide all the OpenPGP keys
>         that were ever mentioned in .guix-authorizations, stored as .key
>         files, which can be either binary or “ASCII-armored”. By
>         default, those .key files are searched for in the branch named
>         keyring but you can specify a different branch name in
>         .guix-channel like so:
>
>
> https://guix.gnu.org/manual/devel/en/guix.html#Specifying-Channel-Authorizations
>
> Cheers,
> simon
>

[-- Attachment #2: Type: text/html, Size: 2854 bytes --]

  reply	other threads:[~2023-06-20  9:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14  1:56 bug#64059: Sudden unexplained error during guix pull: "channel dependency has an invalid introduction field" N. Y.
2023-06-19 14:44 ` Simon Tournier
2023-06-19 17:21   ` N. Y. [this message]
2023-06-20  8:07     ` N. Y.
2023-06-20  9:19 ` Josselin Poiret via Bug reports for GNU Guix
2023-06-23  1:37   ` N. Y.

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='CAEavL=UK+yn8dcB0mEZK-4EtpqDk5UCEgL5ujsscSpaTA=UthQ@mail.gmail.com' \
    --to=ningyuan.sg@gmail.com \
    --cc=64059@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).