Re: guix import crate wraps #:cargo-inputs twice

Dear all, We also have a Rust tool we want to package in Guix, but Rust (like Go and JS) appears to encourage an insane list of dependencies: https://github.com/chfi/rust-qtlreaper/blob/master/Cargo.lock Look at this list. This is for a very simple tool that does some input, output and a computa

Re: Suggest another way of importing GNU Guix GPG key

On Tue, Jul 02, 2019 at 11:54:17AM -0400, Leo Famulari wrote: > This is also being discussed privately with the Guix maintainers. I > expect to push an update for the manual and HACKING today. An update on this: The initial plan is to add the Guix signing key to the new abuse-resistant keyserver

core-updates freeze

Guix, The core-updates branch is now (almost!) ready for prime time. This is turning out to be one of the biggest merges ever[*], currently representing 433 commits from 15 people, with commits dating back to September last year(!). Some of the highlights from this branch include: * jannekes lo

Re: guix import crate wraps #:cargo-inputs twice

Hi Jelle, > On Jul 2, 2019, at 1:05 AM, Jelle Licht wrote: > > Shameless plug; I have some guile code lying around for dealing > with exactly these problems; `guile-semver'[1] might give you a start > for handling these cases. > > [1]: https://notabug.org/jlicht/guile-semver >

Increasing the timeout for shepherd services

Hi everyone, When running Guix in a docker image, I get systematic failures for starting several services: syslogd, nscd, openssh. It turns out that in all these cases the daemons are started, but so slowly that shepherd declares a failure before they are fully operational. I managed to fix this

Re: syslogd can't be started when running Guix in Docker

On 03/07/2019 10:12, Konrad Hinsen wrote: All this suggests that perhaps the problem is not with syslogd, but with shepherd wrongly concluding that syslogd failed. Looks like I will have to dig a bit more into shepherd :-( My hypothesis turned out to be correct: increasing the timeout was su

Re: syslogd can't be started when running Guix in Docker

Hi Maxim, Thanks for your reply! > Try running the Docker container in privileged mode (docker run > --privileged); I think this will allow the necessary Guix services > dependencies of the syslog service to run. I am already running in priviledged mode. Without it, I couldn't build packages. >