unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Dave Love <fx@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: fixing --check saying outputs not valid
Date: Wed, 13 Sep 2017 14:27:17 +0100	[thread overview]
Message-ID: <87k212g24q.fsf@albion.it.manchester.ac.uk> (raw)
In-Reply-To: <87y3pl8mai.fsf@gnu.org> ("Ludovic \=\?iso-8859-1\?Q\?Court\=E8s\?\= \=\?iso-8859-1\?Q\?\=22's\?\= message of "Mon, 11 Sep 2017 14:14:29 +0200")

Ludovic Courtès <ludo@gnu.org> writes:

> Dave Love <fx@gnu.org> skribis:
>>> Then you can run “guix build hwloc --check -L --no-grafts”, which will
>>> build hwloc locally and raise an error if hwloc:{out,lib} are not
>>> bit-identical to what you had in store.
>>
>> [Should that be documented as the procedure to use?]
>
> I think this is documented, but if you think it’s not or not in the
> right place, please tell!

I don't remember where I found out about using --check when packaging.
The manual doesn't mention --no-grafts in connexion with --check as far
as I can see.  I'd add something like

  You probably want to use --check with the --no-grafts option when
  checking a package you are developing, so that it gets rebuilt.

>> The trouble is that I don't get a second build with --check:
>>
>>   $ ./pre-inst-env guix build hwloc --check -L --no-grafts
>                                               ^^^^
> “--no-grafts” is taken as an argument to ‘-L’, and thus you only rebuilt
> the grafting derivation:

Thanks.  I shouldn't just do what I'm told :-/.  However, I don't
understand why -L is needed, or what the path should be.

  reply	other threads:[~2017-09-13 13:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-08  9:34 fixing --check saying outputs not valid Dave Love
2017-09-08 20:56 ` Ludovic Courtès
2017-09-11 10:31   ` Dave Love
2017-09-11 12:14     ` Ludovic Courtès
2017-09-13 13:27       ` Dave Love [this message]
2017-09-14  8:18         ` Ludovic Courtès

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=87k212g24q.fsf@albion.it.manchester.ac.uk \
    --to=fx@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=ludo@gnu.org \
    /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.
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).