bug#27064: SOLVED

2017-05-25 Thread Quiliro
The case is solved. The problem was a bad USB installer. It took 20 minutes to install in a Celeron D with bare-bones.scm Thank all of you that were persistent enough to sugest hundreds of ideas in about 20 installations (some took several hours) and about 13 reboots.

bug#27067: Feature request: please allow for either automatic logging of all output of every guix commands or add an option to each guix command to allow it for all to be logged

2017-05-25 Thread Ricardo Wurmus
Brenton Horne writes: > For example, > `guix pull && guix package -u` has taken up to 12 hours to run for me > before, so if it fails and doesn't log it can be quite an irritating waste > of time and deter people from filing invaluable bug reports about issues > they've experienced with guix. “

bug#27067: Feature request: please allow for either automatic logging of all output of every guix commands or add an option to each guix command to allow it for all to be logged

2017-05-25 Thread Brenton Horne
This feature request isn't specific to guix build (it was low priority to me as I knew it at least had the ability to log, thanks for telling me it automatically does but it doesn't really change this feature request), it's asking for all guix commands with substantial output to automatically log.

bug#27067: Feature request: please allow for either automatic logging of all output of every guix commands or add an option to each guix command to allow it for all to be logged

2017-05-25 Thread Ricardo Wurmus
Brenton Horne writes: > As I understand it only the guix build command has an option to log output > to a file. Actually, the output of “guix build” is indeed stored by default. You can get it by asking for the logs for a given derivation. For example: # build something, please guix b

bug#27067: Feature request: please allow for either automatic logging of all output of every guix commands or add an option to each guix command to allow it for all to be logged

2017-05-25 Thread Brenton Horne
I'm afraid I have no knowledge of Guile or Scheme. Looking at the Guile manual seems to indicate to me it's a language quite unlike most languages I've coded in. The only exception is that it does look a little like Emacs Lisp. On 26 May 2017 at 04:10, Arun Isaac wrote: > > Brenton Horne writes:

bug#27067: Reply to Arun Isaac's reply

2017-05-25 Thread Brenton Horne
Hi, Thanks. This feature would still be useful though, but your idea makes it less urgent. Automatic logging still sounds like a good idea as the Guix package manager is quite slow for some operations at the moment (not criticising the developers of Guix, after all at this early stage of developme

bug#27069: LUKS partition ruined by guix init

2017-05-25 Thread Marius Bakke
some...@selfhosted.xyz writes: > Hi, > > I have several times over tried to install to a LUKS-partition with > btrfs and failed but last time I almost had success. guix init command > complained that the bios_grub flag wasn't set after many hours of > compiling packages and therefore didn't instal

bug#27067: Feature request: please allow for either automatic logging of all output of every guix commands or add an option to each guix command to allow it for all to be logged

2017-05-25 Thread Arun Isaac
> I realize people can already log all output using redirection like > with: > > COMMAND > output.log 2>&1 > > but with this method no output is shown at the command-line so users can't > track what guix is doing in real-time. Somebody else should comment on the feature request. But, for immediat

bug#27069: LUKS partition ruined by guix init

2017-05-25 Thread someone
Hi, I have several times over tried to install to a LUKS-partition with btrfs and failed but last time I almost had success. guix init command complained that the bios_grub flag wasn't set after many hours of compiling packages and therefore didn't install grub at first. I checked the partition w

bug#27067: Feature request: please allow for either automatic logging of all output of every guix commands or add an option to each guix command to allow it for all to be logged

2017-05-25 Thread Brenton Horne
Hi, As I understand it only the guix build command has an option to log output to a file. I would like to request that each guix command have the option at least (if not automatic like it is for Gentoo's Portage package manager) to log all output to a file. I believe this will help both users and

bug#27064: after GuixSD installation

2017-05-25 Thread Quiliro
El Thu, 25 May 2017 00:29:10 -0500 Quiliro escribió: > After installation (with no error mesage), I reboot. These is the output of: > guix system init /mnt/etc/bare-bone.scm /mnt --fallback > http://sprunge.us/SXgC > GrUB starts to boot the system. Then the message > waiting for "my-root" partiti

bug#25882: gcc-wrapper doesn't handle response files

2017-05-25 Thread Ludovic Courtès
Hi Federico, Federico Beffa skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> The attached version adds handling of unreadable files and recursion. >> It does not address parsing of quote-delimited options though, but I’m >> tempted to punt on that one. > > My worry is that not handling the

bug#26987: [PATCH 2/2] build: pull: Fix compilation list construction.

2017-05-25 Thread Ludovic Courtès
Mathieu Othacehe skribis: >> I'm having a hard time tring to understand ,trace output. > > I get why, it's because guile-ssh is not in my %load-path. So loading > "ssh/session.scm" fails in "source-module-dependencies". > > It's a bit of a vicious circle here : if resolve-interface '(ssh > sessio

bug#26948: gnutls errors on multiple guix commands

2017-05-25 Thread Maxim Cournoyer
Hi Ludovic! l...@gnu.org (Ludovic Courtès) writes: > Hi Maxim, > > Maxim Cournoyer skribis: > >> This problem has been ongoing for some time. It prevents me from using >> things such as "guix lint" or "guix import" (seems to be related to >> certs and gnutls). I thought a guix system reconfigure