From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "N. Y." <ningyuan.sg@gmail.com>, 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 11:19:53 +0200 [thread overview]
Message-ID: <87y1ke4hja.fsf@jpoiret.xyz> (raw)
In-Reply-To: <CAEavL=Wrpc=RtEGO5c1QXo27Y7o7-174je1hkOqjcgMp=mT+gw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
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: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-06-20 9:21 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.
2023-06-20 8:07 ` N. Y.
2023-06-20 9:19 ` Josselin Poiret via Bug reports for GNU Guix [this message]
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=87y1ke4hja.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=64059@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=ningyuan.sg@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).