Re: 02/02: gnu: emacs-debbugs: Install missing file.

On 05/30/2017 at 11:30 Alex Kost writes: > alezost pushed a commit to branch master > in repository guix. > > commit 91762db6fe208365e64c32c8eb5d2cfeec36ebed > Author: Alex Kost > Date: Sat May 27 11:31:03 2017 +0300 > > gnu: emacs-debbugs: Install missing file. >

Haskell updates?

Hey Guix, is anyone working on Haskell updates? Looks like we have some catching up to do. -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net

Re: GuixSD Success with grub-efi

James Richardson writes: > I just successfully installed guixsd 0.13.0 with efi on a new HP > laptop. I found the manual to be somewhat lacking with specific details > on exactly how to accomplish this. I've added to my todo list to post > more details here. Thanks for

Re: What’s next?

Ricardo Wurmus skribis: > Ludovic Courtès writes: [...] >> Oops. Here we go: >> >> modified nix/libstore/build.cc >> @@ -2449,8 +2449,11 @@ void DerivationGoal::registerOutputs() >> Hash h2 = recursive ? hashPath(ht, actualPath).first : >>

Re: [PATCH] doc: Move the NGinx service configuration documentation together.

Christopher Baines skribis: > * doc/guix.texi (Web Services): Add documentation for > nginx-upstream-configuration and nginx-location-configuration. > (VPN Services): Remove documentation for nginx-upstream-configuration and > nginx-location-configuration. Applied, thank

Re: "guix system" summary output?

Danny Milosavljevic skribis: >> This sample omits the most useful output, which is the summary of what >> will be done. > > Just tested with the spinner so I could actually (potentially) see the > summary. > > It seems that "guix package" prints such a summary (yay!),

Re: What’s next?

Maxim Cournoyer skribis: > Hi, > > l...@gnu.org (Ludovic Courtès) writes: > >> Hi Brendan, >> >> Brendan Tildesley skribis: >> >>> One little annoyance I have is that guix takes every opportunity to >>> update the list of substitutes

Re: What???s next?

Hi, Maxim Cournoyer skribis: > l...@gnu.org (Ludovic Courtès) writes: > > [...] > >> On GuixSD, the key of hydra.gnu.org and bayfront.guixsd.org are always >> registered by default. We cannot do that for someone installing Guix on >> a foreign distro because that

Re: User-Friendlyness of Guix and non-scaryness, printing messages

Arun Isaac skribis: > Is it possible to have `guix package' NOT build from source? We should definitely add an option for this. See also . Ludo’.

Re: User-Friendlyness of Guix and non-scaryness, printing messages

Hi Danny, Danny Milosavljevic skribis: > And also the spinner integrated: > > diff --git a/guix/scripts/package.scm b/guix/scripts/package.scm > index f050fad97..d9ac61122 100644 > --- a/guix/scripts/package.scm > +++ b/guix/scripts/package.scm > @@ -46,6 +46,7 @@ >

Re: Merge zip.scm into compression.scm

Arun Isaac skribis: > Why does zip and related packages get their own separate file > (gnu/packages/zip.scm)? Why not merge them into > gnu/packages/compression.scm? zip.scm only has 4 packages. I think it would be worth merging, indeed. :-) Would you like to give

Re: Combining Guix, direnv and Emacs for environment customisation

Hi Christopher! Christopher Baines skribis: > direnv [1] is an environment switcher for shells, for example, you want > to have a specific environment variable set when working on a particular > project, you drop a .envrc file in to the relevant directory and > providing

Re: enter debugger on failure

Hi! Ricardo Wurmus skribis: > sometimes Guix crashes. That’s sometimes because of existing bugs > (often in importers) or because I’ve just added something that doesn’t > quite work. > > When Guix crashes it prints a backtrace and exits. Would it be possible > to change

Error when including openexr

Hi guix! I try building a package using openexr. Building fails with /gnu/store/…-openexr-2.2.0/include/OpenEXR/ImfInt64.h:44:24: fatal error: ImathInt64.h: No such file or directory but file …-openexr-2.2.0/include/OpenEXR/ImathInt64.h exists. I discovered that OpenEXR/ImfInt64.h contains

Re: User-Friendlyness of Guix and non-scaryness, printing messages

Arun Isaac writes: >> But I think 'guix package' can be made a lot more user-friendly by not >> showing the build output (by default). The summary of what will be >> installed, and some progress indicator or at least something moving to >> show the user it's doing something, and eventually the

Re: [PATCH] git-download: Fix 'git-predicate' to use absolute paths.

Christopher Baines skribis: > git ls-files will return paths relative to the repository directory. This > commit prepends the repository directory to those paths when calling lstat, > such that 'git-predicate' works if the current working directory is not the > repository

[PATCH] doc: Move the NGinx service configuration documentation together.

* doc/guix.texi (Web Services): Add documentation for nginx-upstream-configuration and nginx-location-configuration. (VPN Services): Remove documentation for nginx-upstream-configuration and nginx-location-configuration. --- doc/guix.texi | 115

Re: "guix system" summary output?

On Tue, 30 May 2017 03:47:46 +0200 Danny Milosavljevic wrote: > > This sample omits the most useful output, which is the summary of what > > will be done. > > Just tested with the spinner so I could actually (potentially) see the > summary. > > It seems that "guix

Re: Add the git commit id to the generation information

Ricardo Wurmus writes: > Hi Roel, > >> I have a feature request. >> >> When I run 'guix pull', install a package, run 'guix pull' again (on >> another day), and install another package, I'd get two generations: >> >>> Generation 181 May 22 2017 11:47:37 >>> + haunt0.2.1 out >>>

Re: Add the git commit id to the generation information

Hi Roel, > I have a feature request. > > When I run 'guix pull', install a package, run 'guix pull' again (on > another day), and install another package, I'd get two generations: > >> Generation 181 May 22 2017 11:47:37 >> + haunt0.2.1 out >>

Re: User-Friendlyness of Guix and non-scaryness, printing messages

> Previously, I thought that the reason that guix prints so much is that > it doesn't log it to a file. But it turns out that it does log it (at > least it has a build log per derivation), also in the failure case. > Why print it then when there's no failure? It doesn't help the user > at all.

`install-file' should print out verbose logs

`install-file' in (guix build utils) should print out verbose logs just as `copy-recursively' does. Something like: (format log-port "~a -> ~a~%" source destination) It's nice to have flowing verbose output when building a package. I believe it is "more reassuring" than waiting at a blank

Re: User-Friendlyness of Guix and non-scaryness, printing messages

Leo Famulari writes: > On Sun, May 28, 2017 at 08:44:44PM +0200, Danny Milosavljevic wrote: >> Ideally, a successful build & installation of a package should look >> like this: >> >> $ guix package -i foobar >> $ > > Silence is golden! > >> Nothing else. If you can't help it, then: >> >> $

Add the git commit id to the generation information

Dear Guix, I have a feature request. When I run 'guix pull', install a package, run 'guix pull' again (on another day), and install another package, I'd get two generations: > Generation 181 May 22 2017 11:47:37 > + haunt0.2.1 out >