From: Pierre Neidhardt <mail@ambrevar.xyz>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org, 38455@debbugs.gnu.org
Subject: Re: [bug#38455] [PATCH] doc: Mention how to test against make / guix pull breakage.
Date: Mon, 02 Dec 2019 13:46:08 +0100 [thread overview]
Message-ID: <87zhgaki9b.fsf@ambrevar.xyz> (raw)
In-Reply-To: <CAJ3okZ3yV9rusCFe7=Or2=oX5bs80eD+6QSTNQZ+KzEsDANN2Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
zimoun <zimon.toutoune@gmail.com> writes:
> On Mon, 2 Dec 2019 at 13:16, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
>>
>> I'm actually not sure about one thing: Does `guix pull` catch the errors
>> of `make`?
>
> What is the point of this advice? Check if "guix pull" is broken,
> right? I think "guix pull -n --url=foo" does the job, isn't it?
>
>> I believe that make can output useful warnings, which maybe not bother
>> `guix pull`, but maybe I'm wrong.
>
> This is another tips? Reading all the points, I feel that another
> point about checking the "make" warnings and/or running the test suite
> should be added.
Why not.
> A good indication is that there is no link to
> "Running the Test Suite".
>
> What do you think?
CC-ing guix-devel.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-12-02 12:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 9:15 [bug#38455] [PATCH] doc: Mention how to test against make / guix pull breakage Pierre Neidhardt
2019-12-02 12:08 ` zimoun
2019-12-02 12:16 ` Pierre Neidhardt
2019-12-02 12:32 ` zimoun
2019-12-02 12:46 ` Pierre Neidhardt [this message]
2019-12-02 12:52 ` zimoun
2019-12-02 12:48 ` zimoun
2019-12-02 19:31 ` Danny Milosavljevic
2019-12-02 20:14 ` Pierre Neidhardt
2019-12-02 21:48 ` Danny Milosavljevic
2019-12-03 10:39 ` zimoun
2019-12-03 10:34 ` zimoun
2019-12-08 15:42 ` Pierre Neidhardt
2019-12-12 15:55 ` zimoun
2019-12-13 12:32 ` Pierre Neidhardt
2019-12-13 12:32 ` Pierre Neidhardt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zhgaki9b.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=38455@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.