GNU bug report logs - #36378
Guix Cuirass Issue with Input channels

Previous Next

Full log

View this message in rfc822 format

From: Ludovic Courtès <ludo <at> gnu.org>
To: "Reza Alizadeh Majd" <r.majd <at> pantherx.org>
Cc: 36378 <at> debbugs.gnu.org
Subject: bug#36378: Guix Cuirass Issue with Input channels
Date: Mon, 01 Jul 2019 11:05:25 +0200

Hello Reza,

"Reza Alizadeh Majd" <r.majd <at> pantherx.org> skribis:

> Package: cuirass
>
> adding additional inputs to cuirass specification with name started with `p` letter, fails the evaluation of specification. 

[...]

> 2019-06-25T19:17:35 evaluating spec 'hello-spec'
> Backtrace:
>           17 (apply-smob/1 #<catch-closure 128b780>)
> In ice-9/boot-9.scm:
>     705:2 16 (call-with-prompt _ _ #<procedure default-prompt-handle…>)
> In ice-9/eval.scm:
>     619:8 15 (_ #(#(#<directory (guile-user) 1316140>)))
>    293:34 14 (_ #(#(#(#(#(#(#(#(#(#(#(…) …) …) …) …) …) …) …) …) …) …))
>     159:9 13 (_ _)
>     619:8 12 (_ #(#(#(#<module (#{ g18}#) 1339640>) #<store-co…> …) …))
>    626:19 11 (_ #(#(#(#<module (#{ g18}#) 1339640>) #<store-co…> …) …))
> In guix/store.scm:
>   1794:24 10 (run-with-store _ _ #:guile-for-build _ #:system _ # _)
> In guix/channels.scm:
>     498:2  9 (_ _)
>     455:2  8 (_ _)
> In guix/monads.scm:
>     482:9  7 (_ _)
> In guix/store.scm:
>    1667:8  6 (_ _)
> In guix/gexp.scm:
>     708:2  5 (_ _)
> In guix/monads.scm:
>     482:9  4 (_ _)
> In guix/gexp.scm:
>    573:13  3 (_ _)
> In guix/store.scm:
>   1667:13  2 (_ _)
> In guix/gexp.scm:
>     210:2  1 (lower-object #f _ #:target _)
>    189:36  0 (lookup-compiler #f)
>
> guix/gexp.scm:189:36: In procedure lookup-compiler:
> In procedure struct_vtable: Wrong type argument in position 1 (expecting struct): #f
>
> Some deprecated features have been used.  Set the environment
> variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
> program to get more information.  Set it to "no" to suppress
> this message.
> 2019-06-25T19:17:36 failed to evaluate spec 'hello-spec'
>
>
> but by just renaming the `pkginput` to something that is not starts with `p` word like `_pkginput` spec evaluation will succeed. 

I find it hard to believe this has anything to do with the name starting
with ‘p’.

If you change back from ‘_pkginput’ to ‘pkginput’, does it fail again?

Thanks,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.