From: "N. Y." <ningyuan.sg@gmail.com>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: 64059@debbugs.gnu.org
Subject: bug#64059: Sudden unexplained error during guix pull: "channel dependency has an invalid introduction field"
Date: Fri, 23 Jun 2023 01:37:01 +0000 [thread overview]
Message-ID: <CAEavL=XM9cpGYzi16mhCX9Rf2OAt=FuCsdvB=fusVaM4hrOvxA@mail.gmail.com> (raw)
In-Reply-To: <87y1ke4hja.fsf@jpoiret.xyz>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
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@jpoiret.xyz> wrote:
> Hi Ning,
>
> "N. Y." <ningyuan.sg@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
>
[-- Attachment #2: Type: text/html, Size: 1690 bytes --]
next prev parent reply other threads:[~2023-06-25 8:46 UTC|newest]
Thread overview: 7+ 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.
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. [this message]
2024-09-10 15:04 ` Simon Tournier
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='CAEavL=XM9cpGYzi16mhCX9Rf2OAt=FuCsdvB=fusVaM4hrOvxA@mail.gmail.com' \
--to=ningyuan.sg@gmail.com \
--cc=64059@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
/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.