Please close this bug report. The underlying problem was a network issue.
Guix is innocent.
Mathieu Othacehe writes:
Hello!
>> Yup, turned out patching GCC was too difficult. I'm experimenting a
>> filter over inputs passed to set-path-environment-variable in set-paths.
>
> This is also quite tricky, because the "libc" input passed to set-paths
> must not be removed from C_INCLUDE_PATH
Marius Bakke writes:
> Hello Mathieu & Ludo,
>
> (+ janneke)
>
> Mathieu Othacehe writes:
>
>>> Yup, turned out patching GCC was too difficult. I'm experimenting a
>>> filter over inputs passed to set-path-environment-variable in set-paths.
>>
>> This is also quite tricky, because the "libc" inp
Hello Mathieu & Ludo,
(+ janneke)
Mathieu Othacehe writes:
>> Yup, turned out patching GCC was too difficult. I'm experimenting a
>> filter over inputs passed to set-path-environment-variable in set-paths.
>
> This is also quite tricky, because the "libc" input passed to set-paths
> must not be
Dear,
Currently, the URI scheme (see 'bioconductor-uri' in
guix/build-system/r.scm) is:
https://bioconductor.org/packages/release/data//src/contrib/-.tar.gz
which leads to 2 issues:
1. when Bioconductor updates their release, some package versions are
updated too, and so, the upstream return
> Yup, turned out patching GCC was too difficult. I'm experimenting a
> filter over inputs passed to set-path-environment-variable in set-paths.
This is also quite tricky, because the "libc" input passed to set-paths
must not be removed from C_INCLUDE_PATH in (gnu packages commencement)
for mes p
