Re: couple of crashes while guix package -u for (libreoffice, kodi, rust, blender)

2018-06-11 Thread Tobias Geerinckx-Rice
ng0, Nils Gillmann wrote: [...] Furthermore it seems like the tor service got somehow broken? I get errors of it not being able to write to its service directory and then crashing. Anyone else experiencing that? Nope. I reconfigured & rebooted my main Tor relay just earlier today, and it's

Re: couple of crashes while guix package -u for (libreoffice, kodi, rust, blender)

2018-06-11 Thread Nils Gillmann
Ricardo Wurmus transcribed 1.3K bytes: > > Hi Nils, > > > * rust is failing a (tiny?) part of its testsuite: > > […] > > note: Run with `RUST_BACKTRACE=1` for a backtrace. > > Have you tried that to see the backtrace? > > > * blender, because of imageio: > > Here you seem to have elided the

Re: couple of crashes while guix package -u for (libreoffice, kodi, rust, blender)

2018-06-11 Thread Ricardo Wurmus
Hi Nils, > * rust is failing a (tiny?) part of its testsuite: > […] > note: Run with `RUST_BACKTRACE=1` for a backtrace. Have you tried that to see the backtrace? > * blender, because of imageio: Here you seem to have elided the actual error message of openimageio. > * kodi (once again, as

couple of crashes while guix package -u for (libreoffice, kodi, rust, blender)

2018-06-11 Thread Nils Gillmann
since HEAD of today (and also 2 days, since I started updating): * rust is failing a (tiny?) part of its testsuite: failures: [run-pass] run-pass/out-of-stack.rs stdout error: test run failed! status: exit code: 101 command:

Re: 04/05: gnu: swig: Patch for Octave 4.4.

2018-06-11 Thread Kei Kebreau
Kei Kebreau writes: > Kei Kebreau writes: > >> Other than Shogun's Python/SWIG-related build failure (attached), this >> patch seems to work fairly well. There appears to be an upstream issue >> related to the invalid conversion mentioned in the build failure. I'm >> keeping an eye on it for

Re: Fwd: Re: Patch file for colorize module

2018-06-11 Thread Sahitihi
Hi Ricardo, Text file is attached with all changes I added including colorize module. The changes added to build.scm is (/(parameterize ((current-build-output-port  colorful-build-output-port)) /) > Please send me the complete changes as a text file, so that I can apply > it to my copy of the

Re: Fwd: Re: Patch file for colorize module

2018-06-11 Thread Sahitihi
Hi Gábor, Updated patch is attached. > Could you send an updated patch? --- Thanks!! Sahithi. >From 765035232a43f09a5c3dbecf77c90499dd1473d4 Mon Sep 17 00:00:00 2001 From: Sahithi Yarlagadda Date: Tue, 5 Jun 2018 00:08:32 +0530 Subject: [PATCH] guix: Add coloring soft port. * guix/ui.scm

Re: GSoC - "Continuing re-write of daemon in Guile Scheme" update

2018-06-11 Thread Joshua Branson
Don't give up! I'm sorry that life has thrown you a curse ball, and I respect your need to help your family. You have still got a lot of potential. And with a little bit of effort, you certainly can contribute to Guix in a meaningful way!

Re: Fwd: Re: Patch file for colorize module

2018-06-11 Thread Ricardo Wurmus
Hi Sahithi, >> You should see the same as I did. > This worked for me too. That’s good. >> To see what’s going on with your modifications to “(guix ui)” it would >> help if you could go through your changes once more (use “git diff” to >> be sure to inspect all the lines you have changed) and

Re: Fwd: Re: Patch file for colorize module

2018-06-11 Thread Gábor Boskovits
2018-06-11 14:14 GMT+02:00 Sahitihi : > Hi Ricardo, > > > You should see the same as I did. > This worked for me too. > > To see what’s going on with your modifications to “(guix ui)” it would > > help if you could go through your changes once more (use “git diff” to > > be sure to inspect all

Re: Fwd: Re: Patch file for colorize module

2018-06-11 Thread Sahitihi
Hi Ricardo, > You should see the same as I did. This worked for me too. > To see what’s going on with your modifications to “(guix ui)” it would > help if you could go through your changes once more (use “git diff” to > be sure to inspect all the lines you have changed) and send your changes > to

Re: GSoC 2018 Syntax and semantics of systemd units in the Shepherd - 1st update

2018-06-11 Thread Ioannis Panagiotis Koutsidis
Thank you a lot for your comments! I will make sure to make the changes that you suggested. As for match and things like car/cdr, I had issues with match and signal handling in the service file, which was why I changed it with a cond. As for the unit parser I also take the rest of the list via

Re: GSoC 2018 Syntax and semantics of systemd units in the Shepherd - 1st update

2018-06-11 Thread Ludovic Courtès
Hello Ioannis! Thanks for the update! Ioannis Panagiotis Koutsidis skribis: > As the 1st phase is coming to an end I decided to post my progress. I have > implemented the unit file parsing as well as some of the basic entries > supported > by it, such as ExecStart, User, Group, Restart, etc.

Re: New ‘guix pull’ dosen’t update the guix manual in GuixSD

2018-06-11 Thread 宋文武
l...@gnu.org (Ludovic Courtès) writes: >> The last there are from the ‘export’ statement of ‘/etc/profile’, the >> first two are added by ‘source’ the profiles. Since there is a guix in >> the system profile contains the old info manual, the current one won’t >> be picked. > > Ooh! I think the

Re: GSoC: Adding a web interface similar to the Hydra web interface

2018-06-11 Thread Ludovic Courtès
Hello Tatiana & Ricardo! Ricardo Wurmus skribis: > I wasn’t sure about this, so I asked on the #guix IRC channel. Ludovic > replied there that the Cuirass repository contains a “random” > specification in “examples/random.scm”. It uses > “examples/random-jobs.scm” to generate … random jobs :)

Re: GSoC: Adding a web interface similar to the Hydra web interface

2018-06-11 Thread Ricardo Wurmus
Hi Tatiana, > I've just committed a new version of the interface. I've implemented the > first feature and create a more friendly interface based on bootstrap. I’ve looked at the screenshots and have to say that this is really looking good already. Exciting! > I had to add new database

Re: 2 ideas

2018-06-11 Thread Nils Gillmann
Chris Marusich transcribed 2.2K bytes: > Ricardo Wurmus writes: > > > It could be useful to have application-specific setup notes in a > > well-known location that is gathered when the profile is built. > > Maybe we could begin by adding a simple, optional field > ("post-install-notes", maybe?)

Re: my latest blog post [everyone, please take a cooldown break]

2018-06-11 Thread swedebugia
Hi On June 10, 2018 4:37:17 PM GMT+02:00, Kei Kebreau wrote: >Gábor Boskovits writes: > >> +1 >> >> 2018-06-10 15:33 GMT+02:00 Christopher Lemmer Webber >: >> >> Nils Gillmann writes: >> >> > Hi, >> > >> > I think it would be best if everyone involved would cool down for >a couple of >> >