all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "宋文武 via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: Christopher Rodriguez <yewscion@gmail.com>,
	57480@debbugs.gnu.org, ludo@gnu.org
Subject: bug#57480: Wrong Type To Apply on Reconfigure
Date: Tue, 30 Aug 2022 14:49:46 +0800	[thread overview]
Message-ID: <87v8qa9qet.fsf@envs.net> (raw)
In-Reply-To: <20220830082045.223b7bd9@sybil.lepiller.eu> (Julien Lepiller's message of "Tue, 30 Aug 2022 08:20:45 +0200")

Julien Lepiller <julien@lepiller.eu> writes:

> I don't know how to fix it, but here is what I think is the issue:
>
> in guix/scripts/system/reconfigure.scm:
>
> #:autoload   (guix describe) (current-channels)
> ...
> (define* (check-forward-update ...
>            (current-channels ...))
>   (define new (current-channels)) ; this is supposed to be the
>          ; autoloaded procedure, but it's the keyword argument
>          ; which is a list
>   ... ; uses of current-channels, the keyword argument
>
> Le Mon, 29 Aug 2022 23:01:46 -0400,
> Christopher Rodriguez <yewscion@gmail.com> a écrit :
>
>> Hello All,
>> 
>> A change made in b084398 is preventing both my system and home
>> configurations from building with a Wrong Type to Apply error. Did the
>> channel spec format change with the changes in that commit?

Hello, I revert the commit b084398 for now.




  reply	other threads:[~2022-08-30  6:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30  3:01 bug#57480: Wrong Type To Apply on Reconfigure Christopher Rodriguez
2022-08-30  6:20 ` Julien Lepiller
2022-08-30  6:49   ` 宋文武 via Bug reports for GNU Guix [this message]
2022-08-30 10:26     ` Wiktor Żelazny
2022-08-30 17:58       ` Christopher Rodriguez
2022-08-31 11:07     ` Ludovic Courtès
2022-08-30 15:09 ` John Kehayias via Bug reports for GNU Guix

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=87v8qa9qet.fsf@envs.net \
    --to=bug-guix@gnu.org \
    --cc=57480@debbugs.gnu.org \
    --cc=iyzsong@envs.net \
    --cc=julien@lepiller.eu \
    --cc=ludo@gnu.org \
    --cc=yewscion@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 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.