unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: csanchezdll@gmail.com (Carlos Sánchez de La Lama)
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Test failure in util-linux
Date: Tue, 14 Apr 2015 12:11:53 +0200	[thread overview]
Message-ID: <7tr3rnkoie.fsf@gmail.com> (raw)
In-Reply-To: <87bnirghd9.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 14 Apr 2015 11:59:46 +0200")

>>>> 2) I tried adding "#:tests? #f" to my own modified ~/guix/linux.scm
>>>> (copied from system-wide
>>>> /usr/local/share/guile/site/2.0/gnu/packages/linux.scm).
>>>> This allowed building with
>>>> "guix package -L $HOME/guix build util-linux"
>>>> but system build still fails during the tests (would seem guix system
>>>> ignores -L flag and takes system-wide recipe).
>>>
>>> Right.  “guix build” now sees your ‘util-linux’ package, but the whole
>>> package DAG uses explicit references to the <package> objects, and so
>>> yours is ignored.
>>>
>>> You may be able to get around it by defining your own (gnu packages
>>> linux) package.  The downside is that it would have to basically be a
>>> copy of the original one with just #:tests? #f added.
>>
>> Hm, thats exactly what I had done (I had copied while linux.scm file,
>> which AFAIU is there (gnu packages linux) is defined, and modified the
>> util-linux package inside it just to ass #:tests? #f. And still guix
>> system does not see it.
>
> Was the module called (gnu packages linux)?  And was GUIX_PACKAGE_PATH
> set when ‘guix system’ was invoked (if ‘sudo’ was used, it could have
> unset it, for instance)?

The package was called (gnu packages linux) as original the linux.scm
file itself was copied in my ~/guix directory., and only #:tests line
added. So the name (and everything else) was the same.

I have a slightly different set-up working so I can not recheck right now,
but I am sure I was not using GUIX_PACKAGE_PATH. I was using the -L
parameter, in both "guix package" (where it worked) and "guix system"
(where it didn't). I tried in both cases passing it directly in the
command line and using the GUIX_BUILD_OPIONS environment variable. That
is what my original guess was that "guix system" did not honor that
parameter.

I had missed GUIX_PACKAGE_PATH in the manual, BTW. Much easier that way.

BR

Carlos

-- 
'[...] es muy distinto lo que una persona quiere, a lo que una persona necesita,
a lo que una persona dice que quiere.'

Javier Castillo, "El día que se perdió la cordura" (2014)

      reply	other threads:[~2015-04-14 10:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09 14:48 Test failure in util-linux Carlos Sánchez de La Lama
2015-04-10 13:09 ` Ludovic Courtès
2015-04-13  7:30   ` Carlos Sánchez de La Lama
2015-04-14  9:59     ` Ludovic Courtès
2015-04-14 10:11       ` Carlos Sánchez de La Lama [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

  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=7tr3rnkoie.fsf@gmail.com \
    --to=csanchezdll@gmail.com \
    --cc=guix-devel@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.
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).