From: zimoun <zimon.toutoune@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Guix pull chokes on uglify-js
Date: Fri, 29 Nov 2019 16:25:36 +0100 [thread overview]
Message-ID: <CAJ3okZ1qVZgbxXa9U4P6y8tCkE+2=EOsOc=k7HY=34SL5n85Ew@mail.gmail.com> (raw)
In-Reply-To: <87pnhahhh6.fsf@ambrevar.xyz>
Hi Pierre,
On Fri, 29 Nov 2019 at 15:58, Pierre Neidhardt <mail@ambrevar.xyz> 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=$HOME/projects/guix --dry-run
> --8<---------------cut here---------------end--------------->8---
>
> does the trick. This is practical and important enough, I suggest we
> add it to the manual in `(guix) 14.6 Submitting Patches'.
>
> Thoughts?
I agree, because it is not the first time that "guix pull" breaks. For
example, this commit 41ca406fa54e69f61c55b11ffe5cf465192a907c reverted
by this one 74e7465c9b3758c1509a3e0dbe575e2014e20f0a.
Document in the manual and maybe add a test in the test-suite (maybe
already exist?)
All the best,
simon
next prev parent reply other threads:[~2019-11-29 15:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 19:58 Guix pull chokes on uglify-js Tobias Geerinckx-Rice
2019-11-28 20:47 ` Pierre Neidhardt
2019-11-29 14:42 ` Pierre Neidhardt
2019-11-29 15:25 ` zimoun [this message]
2019-12-02 9:35 ` Pierre Neidhardt
2019-12-05 12:50 ` Pierre Neidhardt
2019-12-05 14:46 ` Tobias Geerinckx-Rice
2019-12-05 14:54 ` Pierre Neidhardt
2019-12-05 14:55 ` Tobias Geerinckx-Rice
2019-12-05 15:03 ` Pierre Neidhardt
2019-12-05 15:12 ` Marius Bakke
2019-12-05 15:19 ` Pierre Neidhardt
2019-12-05 15:37 ` Pierre Neidhardt
2019-12-05 16:06 ` Tobias Geerinckx-Rice
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ3okZ1qVZgbxXa9U4P6y8tCkE+2=EOsOc=k7HY=34SL5n85Ew@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).