Wrong Type To Apply on Reconfigure

DoneSubmitted by Christopher Rodriguez.
Details
6 participants
  • 宋文武
  • John Kehayias
  • Julien Lepiller
  • Ludovic Courtès
  • Wiktor Żelazny
  • Christopher Rodriguez
Owner
unassigned
Severity
normal
C
C
Christopher Rodriguez wrote on 30 Aug 05:01 +0200
(address . bug-guix@gnu.org)
87pmgiv3dc.fsf@gmail.com
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:


--

Christopher Rodriguez
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEJMQbvYVxvZ0eF/84XZ6FgaGVz3sFAmMNfi8ACgkQXZ6FgaGV
z3tEqA//b4GQUokJR0MM9AaFvfzn7HlA0HiFttD8LYhBbjh5vazAJ0Nx2XHFvp4U
/b5bfmVWzlzSSh1peiFkH5gl79uJdZbjRcxHMXMeoY8iDzIKNgw4aMNa9SUUorkI
Kqz+AJi3IRFxnvQX6DdBLht3W8eBwvdw8H5PsD+S6SgcDRFGUJB5Jka5bhqmBD/y
n+tsGG5UmZ6OrqY/84KVUQubGgcMZ8uZy5RpxPZosSZvhW6VCmms3Bac8Q6SEbCE
fwpk9QyUR4pt8U1JKBqeSA5VfrYXFMwDlMMZycf/Uho4XPi9gr9PwnQWqNQ8Jldn
fmgJg1sGmigS5nFwAp+aNunuGW0RJUyB2g/ZNy4PTZaQ6Kyk4aRIAPQG2aagG2AL
e4aoCHmRAIChUVKh5uWjZXym98zyddPHAabH9o+LPksb2uPsBL+5j7xcPbEGj9RG
EFyB3I5R9LsNpwXAbp/2q4XHeEp0TkCwWqbZfLQz86w7GlZlR33Y3yvlo8XFUHei
EKjvlovdj1/7N8Mcar/p/3QbDWKzHvfQmNjA5g3VWknosE0jta7AopudYcKhVuFV
rlG/M+hgEs1Yixrs73mfW1/xtf7et+GlJW/52sNwVlMQA8M66eJx0S096cHsnpk5
UFC+qNecDgvewSWeNKAYzrjlMmI8A8qjZpBqeu4YnEYhsZgkY0w=
=V/gl
-----END PGP SIGNATURE-----

J
J
Julien Lepiller wrote on 30 Aug 08:20 +0200
(name . Christopher Rodriguez)(address . yewscion@gmail.com)(address . 57480@debbugs.gnu.org)
20220830082045.223b7bd9@sybil.lepiller.eu
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 :

Toggle quote (15 lines)
> 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
宋文武 wrote on 30 Aug 08:49 +0200
(name . Julien Lepiller)(address . julien@lepiller.eu)
87v8qa9qet.fsf@envs.net
Julien Lepiller <julien@lepiller.eu> writes:

Toggle quote (22 lines)
> 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.
W
W
Wiktor Żelazny wrote on 30 Aug 12:26 +0200
(name . 宋文武)(address . iyzsong@envs.net)
20220830102649.fj5fkgsshvqwdisn@nibiowz
On Tue, Aug 30, 2022 at 02:49:46PM +0800, 宋文武 wrote:

Toggle quote (6 lines)
> >> 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?

-----BEGIN PGP SIGNATURE-----

iQKTBAABCgB9FiEEvcl0zdnJun12Glc9xzWoxqtgedUFAmMN5elfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEJE
Qzk3NENERDlDOUJBN0Q3NjFBNTczREM3MzVBOEM2QUI2MDc5RDUACgkQxzWoxqtg
edUmkA/+MKOiiT/bfLkjKBkx/zg0xpsaCXG3r2jeOlFr0AwuMN5eznCVUVUAZhbm
dp+kWlF0Zfw4ssK3kqk5l1Ryrdp1g/9lQVq6J/YBnJWtpuMRXyzbNPi51X5UygXG
cZ/zeRm3Wwzd9POnHigSvTiI6x7vrYQbXz6gMWZQwKGftCyRIc1j6KF/shOE2Z0N
l2tK0K/u81yMeZMnWeoNpbjAd19+PyovFZUpN6ADs/0x6M7c6QsQKppB44IRWrhT
6RG3vMonmvj5t+NPFCVoMuAmde5xRDrssIXg7MDxRiU3pJSFgYE+1yE5gwd+IOWv
IdXy9PHFgcu+W+6CXrpj1mLNs9swIEHQV8rJ6nUQ780/bsdId7WMOKziyUoxn9YO
/xJP5vwL5WDB1bJbEywDJvCalhS6GCtc2hKuIOzNNVw+x994wrxnbcIrZbFiFR/6
7Za8lpSS/q/rt8DTNBH88X+fo/juhXruK53GpQgPHNwqGQrR4qPrRnXF2TrTyMWF
pfr/+02+jwpF/XH3qbQqM6qAcdhtmQV8YlMgHUxzabr7pM6aakYi8QBzKE7qSbGM
eW62uavY7EQGGpswcQGC/R3ys8wr5OJLGdv+Y6aSMPaHyUo8/oKkyAtKySXtGJly
x99Scfaun0mAclT6G26ua4qXZHr2aGoGHCAcgS0X+3bglmOKASU=
=C2Sv
-----END PGP SIGNATURE-----


J
J
John Kehayias wrote on 30 Aug 17:09 +0200
87r10x22g7.fsf@protonmail.com
Hello,

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

Toggle quote (26 lines)
> 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
C
C
Christopher Rodriguez wrote on 30 Aug 19:58 +0200
(name . Wiktor Żelazny)(address . wz@freeshell.de)
87h71tvcfp.fsf@gmail.com
Wiktor Żelazny <wz@freeshell.de> writes:

Toggle quote (3 lines)
> 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
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEJMQbvYVxvZ0eF/84XZ6FgaGVz3sFAmMOUEoACgkQXZ6FgaGV
z3tKLxAAqJcK/0qYauCJQCcKlSaijh9KoFlYowa6E71GXQ5iAib80QnxKxfhm1hr
Cqh2wh6feIAXGNd5QjQuqOj/GWsOlUGj2RYJoegRZWazZ75lGv4F/OJNSnD+cCry
PCXbmGiopd3A4Ddv0tQzOqMiZdrazjcTvXBlZSCsBcYpxysIYXiyQdCtu+ckDcao
8p79IEkwpnpAdxsj3lDbDeh85xL3ahoD8yw2UNzGZPE5A/FM6RR1SfyHwPuZKSeF
e0QG902fpOYIxNNHjR2X4YGWe0MI5QKpKuTL8JnbGNqnh1rcSzSZVQVChvTdYcum
VLF3DFvMLZfZxzXeH2pWchbtSgheBSj3q4Df+EKa1c247NZL1e22mXnCGgaRZ+xx
zjiLxsp7OVK+aaCNmr0a3j6y/y0duLglP8pdukx1tgbpm85KZiWpU8AUJhVYOAf/
S3ophWwCJM0s8l8jhKiU/nRdYF0e8nVRgtB1cvGAi9gdAZTnx13fL67XW7/XEntR
GKoKymiTkAIr1fVdfKjA/hoXGGfloK+p0T7ViB4w2e9effLir92Y8yVbBPjplXGY
adLSsU6nw1xOkqvn6P2bDqkZ6jmCKTTp3ahDwXwGndwB6/1P5RHa0lymKO3xcui1
sNyWkWVYHUfEyrr+wuj3YES9NBV3+3isUQHejL7dYkeOjc8XZWk=
=ED70
-----END PGP SIGNATURE-----

L
L
Ludovic Courtès wrote on 31 Aug 13:07 +0200
(name . 宋文武)(address . iyzsong@envs.net)
877d2obrj3.fsf@gnu.org
Hi,

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

Toggle quote (26 lines)
> 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’.
Closed
?
Your comment

This issue is archived.

To comment on this conversation send email to 57480@debbugs.gnu.org