How to handle armhf time-out on package?

According to https://hydra.gnu.org/build/2447190/nixlog/1/tail-reload we are getting a time-out during testing of dlang ldc on armhf. I admit 3600s for a test is a bit lengthy ;) How to handle this. Should I just disable this test specifically for armhf? It can be done using a switch (s

Re: proposal: with-file-writeable

Marius Bakke skribis: > Gábor Boskovits writes: > >> Ok, the keep it this way. Another question, this came up, as >> I was trying to find a nice solution to reset-gzip-timestamps failing. >> I got different pieces of advice if I should reset the permissions after >> resetting the timestamp, but

Re: How to handle armhf time-out on package?

Pjotr Prins writes: > According to > > https://hydra.gnu.org/build/2447190/nixlog/1/tail-reload > > we are getting a time-out during testing of dlang ldc on armhf. > > I admit 3600s for a test is a bit lengthy ;) > > How to handle this. Should I just disable this test specifically for > armhf

Re: Use guix to distribute data & reproducible (data) science

Hi, > In other words, on the paper, what are the benefits of a management of > some piece of data in the store ? For example for the applications of > weights of a trained neural network; or of the positions of the atoms in > protein structure. Provenance tracking. In a complex data processing wo

Re: How to handle armhf time-out on package?

Hello, Pjotr Prins skribis: > According to > > https://hydra.gnu.org/build/2447190/nixlog/1/tail-reload > > we are getting a time-out during testing of dlang ldc on armhf. > > I admit 3600s for a test is a bit lengthy ;) Indeed, on x86_64, according to

Re: bug#30394: ARM compilation via qemu binfmt - Assertion failure

Hello, Danny Milosavljevic skribis: > Unfortunately, there's a (pretty reproducible) problem with it. > > guix-master/guix $ ./pre-inst-env guix system disk-image --system=armhf-linux > -e "(@ (gnu system install) installation-os)" > [... building grub-2.02 ...] > phase `configure' succeeded af

Graphically isolating Guix containers with Xpra.

Hey Guix, Here's a small tip for how you can create graphically isolated containers with Guix and Xpra. First we create a Xpra server, with no clipboard access. $ xpra start --clipboard=no :200 Next we switch to an empty tmp directory, and start a Guix container that has access to the X200 soc

Re: Use guix to distribute data & reproducible (data) science

On Thu, Feb 15, 2018 at 6:11 PM zimoun wrote: > Hi, > > Thank you for this food for thought. > > > I agree that the frontier between code and data is arbitary. > > However, I am not sure to get the picture about the data management in > the context of Reproducible Science. What is the issue ? > >

Re: core-updates

Hi! Ricardo Wurmus skribis: > I’ve requested a new evaluation of core-updates on hydra because sbcl > and a few other packages have since been fixed. This should show us > fewer packages that we need to worry about before merging core-updates. As of this writing hydra.gnu.org is still building

Re: [PATCH] Add SELinux policy for guix-daemon.

2018-02-16 8:49 GMT+01:00 Alex Vong : > Ricardo Wurmus writes: > > > Alex Vong writes: > > > >>> No, the script won’t install the SELinux policy. It wouldn’t work on > >>> all systems, only on those where a suitable SELinux base policy is > >>> available. > >>> > >> So it won't work on Debian?

Re: Use guix to distribute data & reproducible (data) science

Hi Konrad, On 02/16/2018 at 10:28 Konrad Hinsen writes: > Whether for software or for data, dependencies are DAGs whose terminal > nodes are measuremnts (for data) or human-supplied information (code, > parameters, methodological choices). Guix handles the latter very well. > > The three missing

Re: Use guix to distribute data & reproducible (data) science

Hi George, myg...@gmail.com writes: >> The three missing pieces are: >> >> - Dealing with measurements, which might involve interacting with >>experimental equipment or databases. Moreover, since data from >>such sources can change, its hash in the store must be computed >>from the c

Re: heads-up: Haskell updates

git am just failed because the index is not matching. So I'll not push my core-updates. Next, I tried git merge origin/master which gave me a number of merge conflicts. One of those is gnu/local.mk: + %D%/packages/patches/gettext-multi-core.patch \ + %D%/packages/patches/gette

Re: core-updates

Ludovic Courtès writes: > The weather is OK, though it’s surprisingly lower than what I’d expect > given that everything has been built according to Hydra/Cuirass: The patch for GHC 8 is not yet part of core-updates, which will invalidate a lot of packages. We should get that commit from maste

Re: [PATCH] Add SELinux policy for guix-daemon.

Gábor Boskovits writes: >> > The resulting policy could then be used on GuixSD or any other system >> > that doesn’t have a full SELinux configuration. >> > > I looked around a little, and it seems, that at least Fedora and Debian > has their base policies originated from SELinux reference polic

Re: [PATCH] Add SELinux policy for guix-daemon.

Alex Vong writes: >> These are not things that the daemon needs to have access to. These are >> paths that are to be labeled. The daemon is executed in a certain >> context, and processes in that context may have certain permissions on >> some of the files that have been labeled. >> > I will h

Re: heads-up: Haskell updates

Danny Milosavljevic writes: > git am just failed because the index is not matching. > > So I'll not push my core-updates. > > Next, I tried git merge origin/master which gave me a number of merge > conflicts. > > One of those is gnu/local.mk: > > + %D%/packages/patches/gettext-multi-core.patch

Re: Graphically isolating Guix containers with Xpra.

Hello Rutger, Rutger Helling skribis: > Here's a small tip for how you can create graphically isolated containers > with Guix and Xpra. > > First we create a Xpra server, with no clipboard access. > $ xpra start --clipboard=no :200 > > Next we switch to an empty tmp directory, and start a Guix

Re: heads-up: Haskell updates

Marius Bakke writes: > Should we do a new merge to get the GHC patch, or just merge > core-updates and let the problem "fix itself" on 'master'? I’d prefer building GHC and ghc-resourcet first. We don’t know if this patch actually fixes our problems. We should merge master into core-updates a

Re: heads-up: Haskell updates

Ricardo Wurmus writes: > Marius Bakke writes: > >> Should we do a new merge to get the GHC patch, or just merge >> core-updates and let the problem "fix itself" on 'master'? > > I’d prefer building GHC and ghc-resourcet first. We don’t know if this > patch actually fixes our problems. We shoul

Re: heads-up: Haskell updates

Ricardo Wurmus writes: > Marius Bakke writes: > >> Should we do a new merge to get the GHC patch, or just merge >> core-updates and let the problem "fix itself" on 'master'? > > I’d prefer building GHC and ghc-resourcet first. We don’t know if this > patch actually fixes our problems. We shoul

Re: core-updates

l...@gnu.org (Ludovic Courtès) writes: > Ricardo Wurmus skribis: > >> I’ve requested a new evaluation of core-updates on hydra because sbcl >> and a few other packages have since been fixed. This should show us >> fewer packages that we need to worry about before merging core-updates. > > As of

Re: heads-up: Haskell updates

On Fri, Feb 16, 2018 at 07:12:47PM +0100, Marius Bakke wrote: > Ricardo Wurmus writes: > > > Marius Bakke writes: > > > >> Should we do a new merge to get the GHC patch, or just merge > >> core-updates and let the problem "fix itself" on 'master'? > > > > I’d prefer building GHC and ghc-resource

xorgproto

Hello! X.org recently consolidated the various -proto packages (xproto, xf86driproto, etc) into a single "xorgproto" package: . I'd like to push the attached patch to 'master' and use it for any new packages, and replace xproto

Re: heads-up: Haskell updates

Leo Famulari writes: > On Fri, Feb 16, 2018 at 07:12:47PM +0100, Marius Bakke wrote: >> Ricardo Wurmus writes: >> >> > Marius Bakke writes: >> > >> >> Should we do a new merge to get the GHC patch, or just merge >> >> core-updates and let the problem "fix itself" on 'master'? >> > >> > I’d pre

Re: shepherd logging

Aaand it works on Linux - shepherd messages show up on the console and eventually end up in syslog (I checked). Integration is surprisingly easy and safe (shepherd already does line buffering manually): diff --git a/gnu/packages/admin.scm b/gnu/packages/admin.scm index ccf62a6e2..168495c14 1006

Re: Use guix to distribute data & reproducible (data) science

Hello again Ludovic, On 2018-02-09 18:13, ludovic.cour...@inria.fr wrote: Hi! Amirouche Boubekki skribis: tl;dr: Distribution of data and software seems similar. Data is more and more important in software and reproducible science. Data science ecosystem lakes resources sharing

Re: heads-up: Haskell updates

Mark H Weaver writes: > Ricardo Wurmus writes: > >> Marius Bakke writes: >> >>> Should we do a new merge to get the GHC patch, or just merge >>> core-updates and let the problem "fix itself" on 'master'? >> >> I’d prefer building GHC and ghc-resourcet first. We don’t know if this >> patch act