Re: Status of Gnome upgrade?

Timothy Sample writes: > Hi all, > > I’ve CC’d Kei who has been looking after this. Thanks Kei! > > Brett Gilio writes: > >> Ricardo Wurmus writes: >> >>> Hi Guix, >>> >>> does anyone know what’s holding up the Gnome upgrade? It’s sad to see >>> the upgrade languish when it was almost ready

Re: Packaging Mercury & Some Struggles

Hi Brett, I like having mercury-minimal I think that’s pretty considerate. To use (ice-9 match) you will need to add it to the list of #:modules in the arguments field then use-module in your phase. I.E.: (arguments `( #:modules ,(cons '(ice-9 match) %gnu-build-system-modules) ... Then in

Re: Guix pull chokes on uglify-js

Pierre Neidhardt 写道： Repushed with the last fix in. This time tested against a proper `guix pull`. Pfeww! :) Thank you! You can ignore channels.scm suggestion, was in a hurry $ thought you meant that *--url=* wasn't DTRT. Kind regards, T G-R signature.asc Description: PGP signature

Re: Feedback from JRES in Dijon

Hi, On Thu, 5 Dec 2019 at 16:45, Konrad Hinsen wrote: > > So they are doing physical simulation (fluid dynamics), so they don't > > (can't) get the same result when running the same experiment > > twice. They wart replicability, that is, even if the results are > > different, they are close

Re: Packaging Jami progress

On Thu, 05 Dec 2019 15:32:23 +0100 Pierre Neidhardt wrote: > Thanks! > > The first 5 commits look good overall. Good to know. > For the last one, I think there are a few confusions: > > - native-inputs takes packages or origins, it does not take a lambda. > > - To call a custom function from

Re: Feedback from JRES in Dijon

On Thu, 5 Dec 2019 at 15:43, Julien Lepiller wrote: > So they are doing physical simulation (fluid dynamics), so they don't (can't) > get the same result when running the same experiment twice. They wart > replicability, that is, even if the results are different, they are close > enough to

Re: Feedback from JRES in Dijon

Hi Julien and Pierre, > So they are doing physical simulation (fluid dynamics), so they don't > (can't) get the same result when running the same experiment > twice. They wart replicability, that is, even if the results are > different, they are close enough to each other that you have to draw >

Re: Feedback from JRES in Dijon

Hi Julien, Thank you for this report. On Thu, 5 Dec 2019 at 15:25, Julien Lepiller wrote: > Another wanted to have some kind of doi for guix describe + manifest (a > better UI and easier thing to cite in a paper I suppose). I agree that something is lacking. I was not thinking about DOI but

Re: Guix pull chokes on uglify-js

Pierre Neidhardt writes: > Tobias Geerinckx-Rice writes: > >> Pierre Neidhardt 写道： >>> Let me know if there is anything else that bot broken in the >>> process. >> >> Adding your local repository to ~/.guix/config/channels.scm and >> running ‘guix pull’ after committing (and before pushing)

Re: Guix pull chokes on uglify-js

Tobias Geerinckx-Rice writes: > Pierre Neidhardt 写道： >> Let me know if there is anything else that bot broken in the >> process. > > Adding your local repository to ~/.guix/config/channels.scm and > running ‘guix pull’ after committing (and before pushing) should > reproduce the downstream

Re: Status of Gnome upgrade?

Hi all, I’ve CC’d Kei who has been looking after this. Thanks Kei! Brett Gilio writes: > Ricardo Wurmus writes: > >> Hi Guix, >> >> does anyone know what’s holding up the Gnome upgrade? It’s sad to see >> the upgrade languish when it was almost ready for a merge into master. >> >> Are there

Re: Guix pull chokes on uglify-js

Pierre Neidhardt 写道： Let me know if there is anything else that bot broken in the process. Adding your local repository to ~/.guix/config/channels.scm and running ‘guix pull’ after committing (and before pushing) should reproduce the downstream experience quite accurately, although I

Re: Guix pull chokes on uglify-js

Duh! :( So there is another issue, I'll fix it. Regarding the `guix pull` discussion: it seems that `--dry-run` does not build the package cache (beside many other things) and thus it does not catch many errors. So the trick of running --8<---cut

Re: Guix pull chokes on uglify-js

Pierre, Pierre Neidhardt 写道： I've just pushed ac1ee30f4f7f9d0ae2a655676b0e8b9eb90a35dd to move Lisp libraries to lisp-xyz again, this time fixing the pull issue with the minify build system. Let me know if there is anything else that bot broken in the process. Looks like it: $ guix pull

Re: Feedback from JRES in Dijon

So they are doing physical simulation (fluid dynamics), so they don't (can't) get the same result when running the same experiment twice. They wart replicability, that is, even if the results are different, they are close enough to each other that you have to draw the same scientific

Re: Feedback from JRES in Dijon

I forgot to give you a link to the presentation. It's in French: https://replay.jres.org/videos/watch/c77b3a44-b75f-4c10-9f39-8fb55ae096d7 Also, Marc talked about jdev, another French conference where we could present Guix too: http://devlog.cnrs.fr/jdev2020 Le 5 décembre 2019 15:16:23

Feedback from JRES in Dijon

Hi Guix! I presented the project at JRES yesterday and had lots of questions and reactions. One person was wondering whether Guix would be a good idea for there cluster. I said yes then I redirected them to guix hpc. Another wanted to have some kind of doi for guix describe + manifest (a

Re: Status of Gnome upgrade?

Ricardo Wurmus writes: > Hi Guix, > > does anyone know what’s holding up the Gnome upgrade? It’s sad to see > the upgrade languish when it was almost ready for a merge into master. > > Are there any open issues? Any problems that need solving? I think > this is a high priority item for Guix.

Status of Gnome upgrade?

Hi Guix, does anyone know what’s holding up the Gnome upgrade? It’s sad to see the upgrade languish when it was almost ready for a merge into master. Are there any open issues? Any problems that need solving? I think this is a high priority item for Guix. I’d love to help getting it done.