Re: [PATCH] Add Krita to guix

Disabling the tests worked for me, and this also brings down the compile time, which is already in excess of 1h on my system. On Tue, Dec 5, 2017, at 11:30, Danny Milosavljevic wrote: > Hi, > > On Tue, 05 Dec 2017 02:26:15 +0100 > Mark Meyer wrote: > > > I disabled all tests,

Re: [PATCH] Add Krita to guix

On Tue, Dec 05, 2017 at 11:33:22AM +0100, Mark Meyer wrote: > On Tue, Dec 5, 2017, at 11:30, Danny Milosavljevic wrote: > > Hi, > > > > On Tue, 05 Dec 2017 02:26:15 +0100 > > Mark Meyer wrote: > > > > > I disabled all tests, since these required an X11 display to be present. >

Re: [PATCH] Add Krita to guix

Hi, On Tue, 05 Dec 2017 02:26:15 +0100 Mark Meyer wrote: > I disabled all tests, since these required an X11 display to be present. Does (setenv "QT_QPA_PLATFORM" "offscreen") help? If not, then it's possible to start an X server (Xvfb) in the container, something like

Re: Rust bootstraps via i686?

On Mon, Dec 04, 2017 at 02:56:39PM -0500, Adam Van Ymeren wrote: > Does anyone know why rust bootstraps itself from the i686 version of the > binaries even if you're running on x86_64? > > This results in having to download a build a lot of packages to build > rust on x86_64. > > If I can make

Re: Guix - installation script

what did happen with this ? Was there any progress ?

Re: [PATCH] Add Krita to guix

On Tue, Dec 05, 2017 at 12:57:59PM +0100, Mark Meyer wrote: > I tried enabling test, but sometimes it's easiest to just ask, from the > Krita IRC channel: > > 12:49 < ofosos> hey, I'm trying to package Krita for Guix and I'm > getting a lot > errors, when I activate the check

Re: FOSDEM 2018 and announcing a GNU Guix/Guile day!

Hello everyone, We now have a wiki page for our FOSDEM GNU Guix/Guile day. [1] If you are going to attend please add your name to the wiki, or just respond to this email, so we can order enough lunches! Of course everyone is welcome to come whether they register or not! Also if you know anyone

Re: ISO image available for testing!

Hi Chris, Christopher Baines skribis: > I've attempted to use this to install GuixSD on a Bytemark > VM. Unfortunately I haven't succeeded yet. I managed to get as far as > running guix system init, but when I did, it started downloading the > bootstrap binaries, and then

Re: ISO image available for testing!

Thanks Ludo! But there isn't a i686 ISO :( I'll try install on my x60s. But I'll try on may another PC using x86_64 platform. Thanks, Daniel Pimentel (d4n1)On Dec 5, 2017 8:47 PM, l...@gnu.org wrote: > > Hi Chris, > > Christopher Baines skribis: > > > I've attempted to use

Re: ISO image available for testing!

I'll test it and report here. Thanks, Daniel Pimentel (d4n1)On Dec 5, 2017 8:47 PM, l...@gnu.org wrote: > > Hi Chris, > > Christopher Baines skribis: > > > I've attempted to use this to install GuixSD on a Bytemark > > VM. Unfortunately I haven't succeeded yet. I managed

Re: ISO image available for testing!

Hi Ludovic, l...@gnu.org (Ludovic Courtès) writes: > 91c9b5d01 * packages: 'package-grafts' trims native inputs. [...] > Long story short: we were flagging native inputs as potential sources of > grafts even though, by definition, native inputs are not referred to at > run time. I agree that

Re: ISO image available for testing!

On 06/12/17 10:52, Mark H Weaver wrote: Hi Ludovic, l...@gnu.org (Ludovic Courtès) writes: 91c9b5d01 * packages: 'package-grafts' trims native inputs. [...] Long story short: we were flagging native inputs as potential sources of grafts even though, by definition, native inputs are not

Re: Reducing default verbosity

On Tue, Dec 05, 2017 at 02:33:01PM +0100, Ricardo Wurmus wrote: > * Redirect all build output to log files; as we can’t generally estimate > progress I’d use a spinner and maybe display the name of the current > build phase and the number of build phases that are left. > > Building

Re: native-inputs ending up as run-time references [was: ISO image available for testing!]

On Wed, Dec 06, 2017 at 03:16:45AM +0100, Tobias Geerinckx-Rice wrote: > Hold on. I thought this happened *all the actual time*. > > To me, the output of ‘guix graph’ implies that ghc[*] refers directly to > perl, and ghc-haddock-library to hspec-discover, and that both of those > are native

Re: native-inputs ending up as run-time references [was: ISO image available for testing!]

Leo, Leo Famulari wrote on 06/12/17 at 04:18: > I think of "run-time references" as explicit store references > (file-names) found in the build output by the post-build reference > scanner and recorded in /var/guix/db. These references are what grafting > rewrites. All right, that was my idea

Re: native-inputs ending up as run-time references [was: ISO image available for testing!]

Mark! Ludovic! Mark H Weaver wrote on 06/12/17 at 01:52: > l...@gnu.org (Ludovic Courtès) writes: >> Long story short: we were flagging native inputs as potential >> sources of grafts even though, by definition, native inputs are >> not referred to at run time. > > I agree that this *should*

Re: [PATCH] Add Krita to guix

I tried enabling test, but sometimes it's easiest to just ask, from the Krita IRC channel: 12:49 < ofosos> hey, I'm trying to package Krita for Guix and I'm getting a lot errors, when I activate the check phase of the build. Are these tests

Re: Rust bootstraps via i686?

Efraim Flashner transcribed 2.1K bytes: > On Mon, Dec 04, 2017 at 02:56:39PM -0500, Adam Van Ymeren wrote: > > Does anyone know why rust bootstraps itself from the i686 version of the > > binaries even if you're running on x86_64? > > > > This results in having to download a build a lot of

Re: [PATCH] Add Krita to guix

But in theory it should work with QT_QPA_PLATFORM, this only yields a comparatively small number of failed test in my run, likey 20-30 out of ~200. Cheers, Mark On Tue, Dec 5, 2017, at 12:57, Mark Meyer wrote: > I tried enabling test, but sometimes it's easiest to just ask, from the > Krita IRC

Re: Reducing default verbosity

Hi Ricardo, On Tue, 5 Dec 2017 14:33:01 +0100 Ricardo Wurmus wrote: > * Reduce package downloads from three lines to one line. The > “Downloading URL” line is only important when things go wrong. > * Reduce precision in percentages. The extra digit and the

Reducing default verbosity

Hi Guix, for the release after 0.14.0 I’d like us to implement changes to the default verbosity of Guix commands. Here are a few things that I think would make for better defaults: * Reduce package downloads from three lines to one line. The “Downloading URL” line is only important when