Re: heads-up: Haskell updates

Hi Danny, Danny Milosavljevic writes: > Hi Mark, > Hi Ricardo, > > On Wed, 14 Feb 2018 20:39:12 +0100 > Ricardo Wurmus wrote: > >> Nor do I see this message: >> >> ghc-pkg: unable to decommit memory: Invalid argument > > Which Linux kernel

Re: heads-up: Haskell updates

Mark H Weaver writes: > Given that it's using #ifdef to detect this, I'd expect the result to > depend only on the _headers_ being used to compile, and not the actual > kernel running the build. Is that right? If so, this doesn't explain > why it works for Ricardo but not for

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

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? I think

Re: proposal: with-file-writeable

2018-02-15 15:16 GMT+01:00 Marius Bakke : > 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

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

Gábor Boskovits writes: > 2018-02-15 16:32 GMT+01:00 Ricardo Wurmus : > > 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

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

2018-02-15 16:32 GMT+01:00 Ricardo Wurmus : > > 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

Re: heads-up: Haskell updates

Ricardo Wurmus writes: > Mark H Weaver writes: > >> I suppose if one reads the error message literally: >> >> Control/Monad/Trans/Resource/Internal.hs:302:10: error: >> • Could not deduce (MonadBase IO (Strict.StateT s m)) >> arising from

Re: proposal: with-file-writeable

Gábor Boskovits skribis: > 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 I'm

Re: heads-up: Haskell updates

> I think it just didn't update one of the packages or the package database > and now it got the wrong version where someone changed the type signature > on one side and the other side is stale. Or: Configuring resourcet-1.1.7.5... Warning: This package indirectly depends on multiple versions of

Re: heads-up: Haskell updates

On Thu, Feb 15, 2018 at 12:04:04PM +0100, Danny Milosavljevic wrote: > So I suspect that Ricardo has a Linux >= 4.5 but Andreas and Hydra > have a Linux < 4.5. Is that correct? Strangely not. I am running Guix on Debian with a kernel 4.9.0-5-amd64. Andreas

Re: pull: Update the %sbindir variable in (guix config) when building.

Hi Diego, Diego Nicola Barbato skribis: > From 56d427eefe5c4667ed97b41f6411972b2c6ecc20 Mon Sep 17 00:00:00 2001 > From: Diego Nicola Barbato > Date: Tue, 13 Feb 2018 01:36:40 +0100 > Subject: [PATCH] pull: Update the %sbindir variable in (guix config)

Re: heads-up: Haskell updates

Mark H Weaver writes: > Note that on our 'master' branch we are using Linux-libre-4.4 kernel > headers, but on 'core-updates' we're using 4.9 kernel headers. > > The recently created evaluation 109913 on Hydra is for core-updates with > the recent Haskell changes included.

Re: heads-up: Haskell updates

Hi Mark, Hi Ricardo, On Thu, 15 Feb 2018 03:41:33 -0500 Mark H Weaver wrote: > Given that it's using #ifdef to detect this, I'd expect the result to > depend only on the _headers_ being used to compile, and not the actual > kernel running the build. Yes, that's precisely the

Re: proposal: with-file-writeable

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 I'm still

Re: Improving Shepherd

On Wed 14 Feb 2018 14:10, l...@gnu.org (Ludovic Courtès) writes: > Christopher Lemmer Webber skribis: > >> Ludovic Courtès writes: >> >>> Hopefully it’s nothing serious: Fibers doesn’t rely on anything >>> architecture-specific. >> >> I think it relies on epoll currently?

Re: proposal: with-file-writeable

2018-02-15 14:22 GMT+01:00 Ludovic Courtès : > Gábor Boskovits skribis: > > > 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

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

Hello, Ricardo Wurmus writes: > Catonano writes: > >>> If you want to test this on Fedora, set SELinux to permissive, and make >>> sure to configure Guix properly (i.e. set localstatedir, prefix, and >>> sysconfdir). Then install the policy

Re: heads-up: Haskell updates

Timothy Sample writes: > Unfortunately, I don’t know enough about Haskell to comment on whether > or not these packages “really shouldn’t be overridden” or not. (It > makes sense to me, but OTOH, why are they all split up and on Hackage if > not for tinkering?) If they

Re: heads-up: Haskell updates

Mark H Weaver writes: > So far, almost all of the new packages are building successfully on > Hydra, but I see one failure: ghc-resourcet, which in turn causes > r-bookdown to dep-fail: > > https://hydra.gnu.org/build/2495799/nixlog/1/raw Hmm, how odd. I did build

Re: heads-up: Haskell updates

Ricardo Wurmus writes: > I think that’s a misunderstanding. The cause for the error is earlier > when it complains that some packages depend on different versions of the > “transformers” package. “StateT” is a monad transformer. For what it’s worth, I fixed this error on

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

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? I think Debian and Fedora uses different > base policy, right?

Re: heads-up: Haskell updates

Hi Ricardo, > Danny, could you please do this on master and core-updates? I've done it on master now. Maybe it's me being used to SVN, but can I git am the commit to core-updates? Wouldn't that cause a conflict on the next merge of master to core-updates (because of the missing in-betweens) ?

Re: heads-up: Haskell updates

Danny Milosavljevic writes: > So the only problematic case is that the build process finds MADV_FREE > but the running Linux doesn't yet have it and a ghc program runs on it. > > Reading MADV_DONTNEED docs again, MADV_DONTNEED pretty much does the same > as MADV_FREE -

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

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 ? So, I catch your invitation to explore your idea. :-) Let

Re: Guix Workflow Language ?

Hi, Thank you Ricardo for the pointers and the explanations. Some I already knew. Other not. About Lisp, my heart follows you. My reason is still hesitating. :-) Well, that said :-) I am asking if it should be affordable to organize all the available workflows. For example, two are there

Re: Improving Shepherd

Ludovic Courtès writes: Heya, Jelle Licht skribis: Good news: signfalfd seems to work as far as I can see. I am not quite sure how to make it work consistently with guile ports yet though. Good! What do you mean by “work with guile ports” though? It

Re: Improving Shepherd

Jelle Licht writes: > tl;dr: I cannot seem to block signals from being handled by guile in > some way, which to me seems a prerequisite for using signalfd-based > signal handling. My uneducated guess is that guile needs to support a > way to set signal masks for all threads in

Re: heads-up: Haskell updates

On Thu, Feb 15, 2018 at 06:03:56PM +0100, Danny Milosavljevic wrote: > Hi Ricardo, > > > Danny, could you please do this on master and core-updates? > > I've done it on master now. > > Maybe it's me being used to SVN, but can I git am the commit to core-updates? > > Wouldn't that cause a

Re: heads-up: Haskell updates

Hi Danny, Danny Milosavljevic writes: >> Danny, could you please do this on master and core-updates? > > I've done it on master now. Thank you! > Maybe it's me being used to SVN, but can I git am the commit to > core-updates? Yes. > Wouldn't that cause a conflict on