Re: Guix pull chokes on uglify-js

2019-12-05 Thread Tobias Geerinckx-Rice
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: Guix pull chokes on uglify-js

2019-12-05 Thread Marius Bakke
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) sh

Re: Guix pull chokes on uglify-js

2019-12-05 Thread Pierre Neidhardt
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 exp

Re: Guix pull chokes on uglify-js

2019-12-05 Thread Tobias Geerinckx-Rice
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 haven't

Re: Guix pull chokes on uglify-js

2019-12-05 Thread Pierre Neidhardt
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 here---start-

Re: Guix pull chokes on uglify-js

2019-12-05 Thread Tobias Geerinckx-Rice
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: Guix pull chokes on uglify-js

2019-12-02 Thread Pierre Neidhardt
I've sent patch 38455 to document this. -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

Re: Guix pull chokes on uglify-js

2019-11-29 Thread zimoun
Hi Pierre, On Fri, 29 Nov 2019 at 15:58, Pierre Neidhardt wrote: > > > By the way, is there a convenient way to catch this kind of errors > > without pushing to master first? > > To answer my own question: > > --8<---cut here---start->8--- > guix pull --url=$HO

Re: Guix pull chokes on uglify-js

2019-11-29 Thread Pierre Neidhardt
> By the way, is there a convenient way to catch this kind of errors > without pushing to master first? To answer my own question: --8<---cut here---start->8--- guix pull --url=$HOME/projects/guix --dry-run --8<---cut here---end-

Guix pull chokes on uglify-js

2019-11-28 Thread Tobias Geerinckx-Rice
Pierre, ‘guix pull’ is borken: (repl-version 0 0)Generating package cache for '/gnu/store/n9rwj3jlrf262jgj0ynwf5ihf7kdxvi7-profile'...(exception misc-error (value #f) (value "~A ~S ~S ~S") (value ("No variable named" uglify-js in # 70d17be0>)) (value #f)) mbakke noted that commit ab