bug#57480: Wrong Type To Apply on Reconfigure

bug#57480: Wrong Type To Apply on Reconfigure

[Christopher Rodriguez]

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


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?

Here's my channels.scm: https://paste.debian.net/1252097/

And here's the error message for any commit after b084398:
https://paste.debian.net/1252096/


--

Christopher Rodriguez

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

bug#57480: Wrong Type To Apply on Reconfigure

[Julien Lepiller]

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?
> 
> Here's my channels.scm: https://paste.debian.net/1252097/
> 
> And here's the error message for any commit after b084398:
> https://paste.debian.net/1252096/
> 
> 
> --
> 
> Christopher Rodriguez

bug#57480: Wrong Type To Apply on Reconfigure

[宋文武 via Bug reports for GNU Guix]

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.

bug#57480: Wrong Type To Apply on Reconfigure

[Wiktor Żelazny]

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

On Tue, Aug 30, 2022 at 02:49:46PM +0800, 宋文武 wrote:

> >> 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?
>
> I revert the commit b084398 for now.

Hello,

I’ve got the same problem, and the revert does not seem to help. Isn’t
9096bc28, which modifies gnu/services.scm, the root of the problem?

WŻ

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

bug#57480: Wrong Type To Apply on Reconfigure

[John Kehayias via Bug reports for GNU Guix]

Hello,

On Tue, Aug 30, 2022 at 02:49 PM, 宋文武 wrote:

> 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.

Thanks, I was able to reconfigure after a guix pull to
466038b2e552f5550252afb1a22e3936bc455cfc

John

bug#57480: Wrong Type To Apply on Reconfigure

[Christopher Rodriguez]

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


Wiktor Żelazny <wz@freeshell.de> writes:

> I’ve got the same problem, and the revert does not seem to help. Isn’t
> 9096bc28, which modifies gnu/services.scm, the root of the problem?

I was able to successfully reconfigure with the 9096bc28 commit, but
maybe I don't use what was changed in it in my configurations.

They /do/ seem related, but I am not familiar enough with what was
changed to speculate as to a solution for either issue.

--

Christopher Rodriguez

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

bug#57480: Wrong Type To Apply on Reconfigure

[Ludovic Courtès]

Hi,

宋文武 <iyzsong@envs.net> skribis:

> 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.

Thanks for the quick reaction.

As Julien wrote, the code referred to the wrong ‘current-channels’.
Fixed in 270e1b9e1ea2b3e41067a38b094b0656ceb56838.

Ludo’.