GNU bug report logs - #64059
Sudden unexplained error during guix pull: "channel dependency has an invalid introduction field"

Previous Next

Package: guix;

Reported by: "N. Y." <ningyuan.sg <at> gmail.com>

Date: Wed, 14 Jun 2023 02:40:03 UTC

Severity: normal

Done: Simon Tournier <zimon.toutoune <at> gmail.com>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 64059 in the body.
You can then email your comments to 64059 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#64059; Package guix. (Wed, 14 Jun 2023 02:40:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to "N. Y." <ningyuan.sg <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Wed, 14 Jun 2023 02:40:03 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "N. Y." <ningyuan.sg <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: Sudden unexplained error during guix pull: "channel dependency has an
 invalid introduction field"
Date: Wed, 14 Jun 2023 01:56:12 +0000
[Message part 1 (text/plain, inline)]
Hi all,

I am suddenly having errors with guix pull while pulling my own custom
channels, after upgrading guix yesterday. My custom channels has not
changed since early April. I am sure I was able to pull from my custom
channels when I last upgraded around early June.

The error is "channel dependency has an invalid introduction field," but
the introduction fields of my custom channels have the same form as those I
use for GNU guix and nonguix channels which I can pull without errors; and
the channel introductions and GPG fingerprints are unchanged from the last
time I was able to pull successfully (I have the channels.scm file under
version control).

There are two private channels. Including either of them are sufficient to
replicate the error; at least one is necessary to replicate the error.

Command line output:

ning <at> bluecoral ~/roamdb/notes/tasks$ guix pull
Updating channel 'guix' from Git repository at '
https://git.savannah.gnu.org/git/guix.git'...
Updating channel 'nonguix' from Git repository at '
https://gitlab.com/nonguix/nonguix'...
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

ning <at> bluecoral ~/roamdb/notes/tasks$ guix --version
guix (GNU Guix) b94cbbbce70f59b795526a0ed305facf041e6faa
Copyright (C) 2023 the Guix authors
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

ning <at> bluecoral ~/roamdb/notes/tasks$ cat ~/.config/guix/channels.scm
(list (channel
        (name 'guix)
        (url "https://git.savannah.gnu.org/git/guix.git")
        (branch "master")
        (introduction
          (make-channel-introduction
            "9edb3f66fd807b096b48283debdcddccfea34bad"
            (openpgp-fingerprint
              "BBB0 2DDF 2CEA F6A8 0D1D  E643 A2A0 6DF2 A33A 54FA"))))
      (channel
        (name 'nonguix)
        (url "https://gitlab.com/nonguix/nonguix")
        (branch "master")
        (introduction
          (make-channel-introduction
            "897c1a470da759236cc11798f4e0a5f7d4d59fbc"
            (openpgp-fingerprint
              "2A39 3FFF 68F4 EF7A 3D29  12AF 6F51 20A0 22FB B2D5"))))
      (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"))))
      (channel
        (name 'ninguix-private)
        (url "git <at> github.com:ning-y/ninguix-private.git")
        (branch "main")
        (introduction
          (make-channel-introduction
            "01f91f7dba5a4949a0719e0ff0e85bb8b0050128"
            (openpgp-fingerprint
              "4523 A758 035C 5177 7A8F  1E1F 2CB0 E8CD 7035 5FB7")))))
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#64059; Package guix. (Mon, 19 Jun 2023 16:37:03 GMT) Full text and rfc822 format available.

Message #8 received at 64059 <at> debbugs.gnu.org (full text, mbox):

From: Simon Tournier <zimon.toutoune <at> gmail.com>
To: "N. Y." <ningyuan.sg <at> gmail.com>, 64059 <at> debbugs.gnu.org
Subject: Re: bug#64059: Sudden unexplained error during guix pull: "channel
 dependency has an invalid introduction field"
Date: Mon, 19 Jun 2023 16:44:39 +0200
Hi,

On Wed, 14 Jun 2023 at 01:56, "N. Y." <ningyuan.sg <at> 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




Information forwarded to bug-guix <at> gnu.org:
bug#64059; Package guix. (Mon, 19 Jun 2023 17:23:01 GMT) Full text and rfc822 format available.

Message #11 received at 64059 <at> debbugs.gnu.org (full text, mbox):

From: "N. Y." <ningyuan.sg <at> gmail.com>
To: Simon Tournier <zimon.toutoune <at> gmail.com>
Cc: 64059 <at> debbugs.gnu.org
Subject: Re: bug#64059: Sudden unexplained error during guix pull: "channel
 dependency has an invalid introduction field"
Date: Tue, 20 Jun 2023 01:21:58 +0800
[Message part 1 (text/plain, inline)]
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 <at> gmail.com> wrote:

> Hi,
>
> On Wed, 14 Jun 2023 at 01:56, "N. Y." <ningyuan.sg <at> 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
>
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#64059; Package guix. (Tue, 20 Jun 2023 08:09:02 GMT) Full text and rfc822 format available.

Message #14 received at 64059 <at> debbugs.gnu.org (full text, mbox):

From: "N. Y." <ningyuan.sg <at> gmail.com>
To: 64059 <at> debbugs.gnu.org
Cc: Simon Tournier <zimon.toutoune <at> gmail.com>
Subject: Re: bug#64059: Sudden unexplained error during guix pull: "channel
 dependency has an invalid introduction field"
Date: Tue, 20 Jun 2023 08:07:46 +0000
[Message part 1 (text/plain, inline)]
I was able to pull my custom channels without error after pinning the GNU
Guix repository (https://git.savannah.gnu.org/git/guix.git) to commit
f2e98587 (21 May). The Guix CLI version for this commit was version
d884fc9e2efecfba09af4694f5a13ad7fc6f704f.

(channel
        (name 'guix)
        (url "https://git.savannah.gnu.org/git/guix.git")
        ; (branch "master")
        (commit "f2e98587ec72b5f5c2ec79956ced129350396bab")
        (introduction
          (make-channel-introduction
            "9edb3f66fd807b096b48283debdcddccfea34bad"
            (openpgp-fingerprint
              "BBB0 2DDF 2CEA F6A8 0D1D  E643 A2A0 6DF2 A33A 54FA"))))

ning <at> bluecoral ~/repos/guix$ guix --version
guix (GNU Guix) d884fc9e2efecfba09af4694f5a13ad7fc6f704f
Copyright (C) 2023 the Guix authors
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

On Mon, Jun 19, 2023 at 5:21 PM N. Y. <ningyuan.sg <at> gmail.com> wrote:

> 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 <at> gmail.com>
> wrote:
>
>> Hi,
>>
>> On Wed, 14 Jun 2023 at 01:56, "N. Y." <ningyuan.sg <at> 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
>>
>
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#64059; Package guix. (Tue, 20 Jun 2023 09:21:02 GMT) Full text and rfc822 format available.

Message #17 received at 64059 <at> debbugs.gnu.org (full text, mbox):

From: Josselin Poiret <dev <at> jpoiret.xyz>
To: "N. Y." <ningyuan.sg <at> gmail.com>, 64059 <at> debbugs.gnu.org
Subject: Re: bug#64059: Sudden unexplained error during guix pull: "channel
 dependency has an invalid introduction field"
Date: Tue, 20 Jun 2023 11:19:53 +0200
[Message part 1 (text/plain, inline)]
Hi Ning,

"N. Y." <ningyuan.sg <at> gmail.com> writes:

> The error is "channel dependency has an invalid introduction field," but
> the introduction fields of my custom channels have the same form as those I
> use for GNU guix and nonguix channels which I can pull without errors; and
> the channel introductions and GPG fingerprints are unchanged from the last
> time I was able to pull successfully (I have the channels.scm file under
> version control).

I've purposefully added this new error to warn users that their
.guix-channel's introduction forms were erroneous.  Previously, they
were silently being dropped.  The formats in a channels.scm file and in
the .guix-channel file are *not* the same!  Please see "(guix) Declaring
Channel Dependencies" for an example of the format.

Best,
-- 
Josselin Poiret
[signature.asc (application/pgp-signature, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#64059; Package guix. (Fri, 23 Jun 2023 01:38:01 GMT) Full text and rfc822 format available.

Message #20 received at 64059 <at> debbugs.gnu.org (full text, mbox):

From: "N. Y." <ningyuan.sg <at> gmail.com>
To: Josselin Poiret <dev <at> jpoiret.xyz>
Cc: 64059 <at> debbugs.gnu.org
Subject: Re: bug#64059: Sudden unexplained error during guix pull: "channel
 dependency has an invalid introduction field"
Date: Fri, 23 Jun 2023 01:37:01 +0000
[Message part 1 (text/plain, inline)]
Hi Josselin,

Thank you so much for your help! Indeed, the .channels.scm files of my
custom channels had invalid introduction fields. That's on me --- I
should've read the error message more carefully!

Best regards,
Ning

On Tue, Jun 20, 2023 at 9:19 AM Josselin Poiret <dev <at> jpoiret.xyz> wrote:

> Hi Ning,
>
> "N. Y." <ningyuan.sg <at> gmail.com> writes:
>
> > The error is "channel dependency has an invalid introduction field," but
> > the introduction fields of my custom channels have the same form as
> those I
> > use for GNU guix and nonguix channels which I can pull without errors;
> and
> > the channel introductions and GPG fingerprints are unchanged from the
> last
> > time I was able to pull successfully (I have the channels.scm file under
> > version control).
>
> I've purposefully added this new error to warn users that their
> .guix-channel's introduction forms were erroneous.  Previously, they
> were silently being dropped.  The formats in a channels.scm file and in
> the .guix-channel file are *not* the same!  Please see "(guix) Declaring
> Channel Dependencies" for an example of the format.
>
> Best,
> --
> Josselin Poiret
>
[Message part 2 (text/html, inline)]

Reply sent to Simon Tournier <zimon.toutoune <at> gmail.com>:
You have taken responsibility. (Tue, 10 Sep 2024 16:20:20 GMT) Full text and rfc822 format available.

Notification sent to "N. Y." <ningyuan.sg <at> gmail.com>:
bug acknowledged by developer. (Tue, 10 Sep 2024 16:20:21 GMT) Full text and rfc822 format available.

Message #25 received at 64059-done <at> debbugs.gnu.org (full text, mbox):

From: Simon Tournier <zimon.toutoune <at> gmail.com>
To: "N. Y." <ningyuan.sg <at> gmail.com>
Cc: 64059-done <at> debbugs.gnu.org, Josselin Poiret <dev <at> jpoiret.xyz>
Subject: Re: bug#64059: Sudden unexplained error during guix pull: "channel
 dependency has an invalid introduction field"
Date: Tue, 10 Sep 2024 17:04:41 +0200
Hi,

On Fri, 23 Jun 2023 at 01:37, "N. Y." <ningyuan.sg <at> gmail.com> wrote:

>>  I've purposefully added this new error to warn users that their
>>  .guix-channel's introduction forms were erroneous.  Previously, they
>>  were silently being dropped.  The formats in a channels.scm file and in
>>  the .guix-channel file are *not* the same!  Please see "(guix) Declaring
>>  Channel Dependencies" for an example of the format.

[...]

> Thank you so much for your help! Indeed, the .channels.scm files of my
> custom channels had invalid introduction fields. That's on me --- I
> should've read the error message more carefully!

Therefore closing.

Feel free to reopen if I have misunderstood.

Cheers,
simon




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Wed, 09 Oct 2024 11:24:10 GMT) Full text and rfc822 format available.

This bug report was last modified 48 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.