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

On Fri, Feb 9, 2018 at 8:16 PM Konrad Hinsen wrote: > Hi, > > On 09/02/2018 18:13, Ludovic Courtès wrote: > > > Amirouche Boubekki skribis: > > > >> tl;dr: Distribution of data and software seems similar. > >> Data is more and more important in software and reproducible > >> scie

Re: Call for project proposals: Guix and Outreachy

Chris Marusich writes: > Gábor Boskovits writes: > >> 5. explore orchestration in guix - I think Chris could be interested in >> this, and I am also willing to help. >> 6. explore provisioning in guix - provisioning from cloud provides >> essentially boils down to talking to apis, but I would b

Re: Let's fix core-updates!

Hi Chris, thank you for taking the initiative! > Currently, 13% of builds on core-updates fail: > > https://hydra.gnu.org/jobset/gnu/core-updates This may be a better URL: https://hydra.gnu.org/eval/109908?full=1&compare=master It is a list of build failures that happen on core-updates b

Re: Cuirass news

Hi Danny, Danny Milosavljevic skribis: > the patch LGTM! Pushed! >>I’d reluctant to ‘sqlite-uncache!’ though. > > I was thinking if you are in the REPL and actually want it to forget the > statement which you cached before, it would be good to be able to do that. > I wonder what I was thinking

Re: Let's fix core-updates!

Ricardo Wurmus writes: >> Currently, 13% of builds on core-updates fail: >> >> https://hydra.gnu.org/jobset/gnu/core-updates > > This may be a better URL: > >https://hydra.gnu.org/eval/109908?full=1&compare=master If you cannot access this because hydra is timing out, then try this copy:

Re: Let's fix core-updates!

Chris Marusich writes: > Hi everyone! > > Currently, 13% of builds on core-updates fail: > > https://hydra.gnu.org/jobset/gnu/core-updates > > We need to fix this to help Ricardo prepare for the next release. > Questions: > > 1) When is core-updates "done"? Do we merge once we're below a >

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

Hi, Thank you for the topic feeding my thoughts. And thank you Ricardo for your explanations. > What I was thinking about, is use guix to distribute data packages just like > we distribute softwares from pypi. The advantage of using guix seems > obvious, > but apparantly it's not desirable or pos

Re: Improving Shepherd

Hey all, 2018-02-05 14:08 GMT+01:00 Ludovic Courtès : > Hello! > > [...] > > Currently shepherd monitors SIGCHLD, and it’s not supposed to miss > those; in some cases it might handle them later than you’d expect, which > means that in the meantime you see a zombie process, but otherwise it > seem

my server crashed

Hi, as we have at least 2 packages (or 1? I have a large number of packages I need to upstream...) that were hosted on my server I just wanted to inform you that I'll send updates to the URLs once I have the new server up and running. The old Debian had a fatal crash I couldn't bother to recover f

proposal: modularize unpack in gnu build system

It seems, that currently we don't have zip in gnu build system, so that ends up in native-inputs, if we need that to unpack the tarball. It would be nice if gnu-build-system would use the appropriate compressor, and at the same time only depend on the one needed. How could this be achieved? We al

proposal: with-file-writeable

the make-file-writeable function seems a bit too imperative to me, it would look better if we could have a with-file-writeable function, so that we can constrain the size effect, and more. Moreover if a file is read-only to start with, it might be a good idea to keep it that way anyways. WDYT?

Re: Let's fix core-updates!

Marius Bakke writes: > * SBCL: > > I don't know anything about this package, so not sure what to do about > it. It has 45 dependents, including MATE, so merging without it is not > great. I tried updating to the latest versio

Re: ARM compilation via qemu binfmt - Assertion failure

Danny Milosavljevic writes: > This is only fixed in glibc 2.27 (not in core-updates). Should we upgrade glibc in core-updates, then? Or is it better to do it in the next core-updates cycle, to avoid still more unexpected breakage? -- Chris signature.asc Description: PGP signature

How to notice when my change breaks something (was: Re: 02/05: gnu: luajit: Update to 2.1.0-beta3.)

Hi Mark, How do you notice when a change breaks something else? You so frequently notice these things, it almost seems like you're omniscient! Do you have an automated mechanism for doing this, or are you manually checking things frequently? We should all be able to do this, but I suspect some

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

On Sun, Feb 11, 2018 at 12:45:18AM +0100, Chris Marusich wrote: > Danny Milosavljevic writes: > > > This is only fixed in glibc 2.27 (not in core-updates). > > Should we upgrade glibc in core-updates, then? Or is it better to do it > in the next core-updates cycle, to avoid still more unexpecte

Re: Defining shepherd user services -- feedback desired

l...@gnu.org (Ludovic Courtès) writes: >> (define (services->package services) >> "Yield a package for SERVICES by making them into a shepherd >> configuration file via scheme-file." > > This makes me think that perhaps we should generalize profile, and allow > non-package objects in there—it do