Pushed, closing.
Hi,
Clément Lassieur writes:
> Attached is a patch that makes sure the checkout is from the Guix input
> providing the 'proc'.
I'll push this tomorrow if nobody objects.
Thanks,
Clément
Clément Lassieur writes:
>> So it's indeed a bug in Guix, introduced by commit
>> b5f8c2c88543158e8aca76aa98f9009f6b9e743a (hydra: Compute jobs in an
>> inferior). We can't just take the first input we find, build it and
>> open an inferior for it. I believe we should take the input whose name
Clément Lassieur writes:
> So it's indeed a bug in Guix, introduced by commit
> b5f8c2c88543158e8aca76aa98f9009f6b9e743a (hydra: Compute jobs in an
> inferior). We can't just take the first input we find, build it and
> open an inferior for it. I believe we should take the input whose name
>
Hi Reza and Ludo,
Reza Alizadeh Majd writes:
> adding additional inputs to cuirass specification with name started
> with `p` letter, fails the evaluation of specification.
Thank you for reporting this! It actually fails with names that come
after the first input (in this case: "guix") in
Hi,
Does anyone checked steps to reproduce this issue?
Is it occur for anyone else?
Best,
Reza
Hi Ludo,
>
> 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?
>
yes, renaming the input name back to `pkginput` I received same error
again.
It is so strange for me, but I had
Hello Reza,
"Reza Alizadeh Majd" 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
