Re: guix pull failed after 8 hours

Konrad Hinsen writes: > Hi Ludo and Chris, > >> Could it be that those old systems were talking to hydra.gnu.org and >> thus not getting any substitutes? >> >> https://lists.gnu.org/archive/html/info-guix/2019-06/msg1.html > > That's what happened to me on my oldest Guix installation

Re: State of the powerpc64le port

Hello, For your information, I already did proceed to porting to powerpc64le-linux some time ago. Here's where my work is : https://gitlab.com/lle-bout/guix The `core-updates` branch contains the latest changes, you can also observe CI pipelines to get build logs for both GNU Guix itself

State of the powerpc64le port

Hello fellow Guix hackers, recently I just gave the powerpc64le-linux thing another try, as I'm missing Guix to much on my main machine (POWER9)... Work is happening on a personal branch. It still in a WIP state and force-pushing can occur:

Re: 79-GiB opam checkout in ~/.cache/guix

Hi Tobias, On +2019-11-18 23:58:10 +0100, Tobias Geerinckx-Rice wrote: > Auntie Guix, > > My SSD hurts & my ~/.cache/guix feels funny: > > ~ λ du -hs ~/.cache/guix/checkouts/* | sort -h > 560K /home/nckx/.cache/guix/checkouts/hp4… > 1.3M /home/nckx/.cache/guix/checkouts/l74… > 2.5M

79-GiB opam checkout in ~/.cache/guix

Auntie Guix, My SSD hurts & my ~/.cache/guix feels funny: ~ λ du -hs ~/.cache/guix/checkouts/* | sort -h 560K /home/nckx/.cache/guix/checkouts/hp4… 1.3M /home/nckx/.cache/guix/checkouts/l74… 2.5M /home/nckx/.cache/guix/checkouts/hep… 219M /home/nckx/.cache/guix/checkouts/pjm… 79G

Re: help with a confusing error: url-fetch, hash, invalid keyword #vu8

Hi Robert, Excellent! Glad that helped :D. - John

Re: help with a confusing error: url-fetch, hash, invalid keyword #vu8

On 18. Nov 2019, at 21:40, John Soo wrote: > > Hi Robert, > > Interesting. Looks alright to me. Also I did just package ormolu myself and > everything worked alright. One thing to try is using `guix repl` to reproduce > the error. Can you open one up and see what happens? Actually that

Re: help with a confusing error: url-fetch, hash, invalid keyword #vu8

Hi Robert, Interesting. Looks alright to me. Also I did just package ormolu myself and everything worked alright. One thing to try is using `guix repl` to reproduce the error. Can you open one up and see what happens? - John

Re: Speaking about Guix at NL-RSE 2019

> Sure, take whatever you find useful from > . > > In the context of this conference it probably makes sense to discuss > how Guix fits in the big picture of reproducible science (as in the > aramis-2019 and jcad-2018

Re: Package inputs in manifests

Hi, On Mon, 18 Nov 2019 at 00:12, Bengt Richter wrote: > Can "collisions" be collisions even if the targets are bit-identical? I think yes. --8<---cut here---end--->8--- $ find -P /gnu/store -maxdepth 1 -name "*gzip-1.9" -type d -print

Re: wip blog post (v2): running Guix System on ARM

Hi Julien, On Sun, 17 Nov 2019 17:57:28 +0100 Julien Lepiller wrote: > Thank you! attached is a new version of that blog post. I think I'll > convert it to texinfo and add it to the cookbook, instead of making it > a blog post, as we then could change or remove it more easily if we > make

Re: Package inputs in manifests

Hi, On Sun, 17 Nov 2019 at 11:35, Ludovic Courtès wrote: > You’re doing it right! It turns out that two different variants of > “gzip” appear: one in ‘%final-inputs’ (the implicit inputs of > ‘gnu-build-system’) and another one somewhere else, hence the collision. > > The solution is to pass

help with a confusing error: url-fetch, hash, invalid keyword #vu8

Hi, I’m in writing up some notes on my Guix packaging work earlier this year, and am running into an unexpected problem that I’m lost with. A concrete example: $ guix import hackage ormolu > ormolu.scm add missing imports at the top of ormolu.scm: (use-modules (guix packages)) (use-modules

Re: Profiles/manifests-related command line interface enhancements

Hi, On Sun, 17 Nov 2019 at 12:30, Konrad Hinsen wrote: > If enough people are willing to work on this (beginners included!), we > could run a "CLI working group" that plays with alternatives to the > current CLI, implemented as a separate Guile package so it won't perturb > business as usual.

Re: Profiles/manifests-related command line interface enhancements

Hi Konrad, On Sun, 17 Nov 2019 at 11:45, Konrad Hinsen wrote: > For a long version of these arguments, see >https://hal.archives-ouvertes.fr/hal-01966145/document Thank you for the pointer. I missed it months ago. :-) So, you propose to "enrich" the DSL describing the manifest files,

Re: Profiles/manifests-related command line interface enhancements

On Sat, 16 Nov 2019 at 23:27, Ludovic Courtès wrote: > > Me too :-) It's "guix package" that is the worst offender in my > > opinion. It does two distinct things: querying the package database and > > managing profiles. And now that we have "guix search" for queries, > > We also have ‘guix

Re: guix package: Rename "generation" options

Hi, On Sun, 17 Nov 2019 at 11:59, Ludovic Courtès wrote: > That said, I agree that the inconsistency is troubling. Would it be > better to have ‘guix list-generations’, etc.? Or maybe that ‘guix > profile’ command that has been proposed before? Let add this to the current big discussion on

Re: Mailman packaging (was: Re: Python package naming: Dots vs hyphens)

Thank you for your work and for looking at projects’ mailing lists etc. :) I still have not set up mailman on my server, but am still going to work on it. I agree everywhere except the non-free emails and a typo in a description, see below. On Mon, Nov 18, 2019 at 12:13:51PM +0200, Efraim

Re: Why is the default $HOME /homeless-shelter?

Hi Jesse, Jesse Gibbons writes: > On Sun, 2019-11-17 at 22:39 +0100, Ludovic Courtès wrote: >> Hi! >> >> Because it’s always been this way! :-) >> >> This is inherited from Nix. The rationale is that there’s no home >> directory in build environments, and perhaps Eelco Dolstra and others >>

Re: Overhauling the cargo-build-system

On Sun, Nov 17, 2019 at 10:22:21PM +0100, Ludovic Courtès wrote: > Hi, > > Efraim Flashner skribis: > > > The big problems are the recursive dependencies, the partial > > dependencies and the versioning. There are some that are easy to figure > > out, serde always needs serde-derive, winapi

Re: Mailman packaging (was: Re: Python package naming: Dots vs hyphens)

On Wed, Nov 06, 2019 at 02:18:33PM +0100, pelzflorian (Florian Pelz) wrote: > Long e-mail / review follows. Feel free to disagree. > > On Wed, Nov 06, 2019 at 09:19:17AM +0200, Efraim Flashner wrote: > > On Wed, Nov 06, 2019 at 07:49:56AM +0100, pelzflorian (Florian Pelz) wrote: > > > I am in

Re: [PATCH 1/2] Support publishing build events

Ludovic Courtès writes: > Hi! > > Christopher Baines skribis: > >>> IIUC, the ‘send-events’ program is provided as a debugging aid, right? >>> I mean it’s not used anywhere in the code. >> >> Well, it would be potentially better to send the events from the same >> Cuirass process that manages

Re: wip blog post: running Guix System on ARM

On Sun, Nov 17, 2019 at 08:43:33PM +0100, Ludovic Courtès wrote: > Hello! > > Julien Lepiller skribis: > > > Hi, attached is a draft for a blog post (or a section in the cookbook) > > for explaining how to install the Guix System on an ARM board. WDYT? > > I really like it! Yes, it makes we