all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Dave Love <fx@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: fixing --check saying outputs not valid
Date: Thu, 14 Sep 2017 10:18:26 +0200	[thread overview]
Message-ID: <874ls5d771.fsf@gnu.org> (raw)
In-Reply-To: <87k212g24q.fsf@albion.it.manchester.ac.uk> (Dave Love's message of "Wed, 13 Sep 2017 14:27:17 +0100")

Dave Love <fx@gnu.org> skribis:

> 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.

-L is not needed, it was a typo on my side.

Thanks,
Ludo’.

      reply	other threads:[~2017-09-14  8:18 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
2017-09-14  8:18         ` Ludovic Courtès [this message]

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=874ls5d771.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=fx@gnu.org \
    --cc=help-guix@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.
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.