[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Test failure in util-linux
From: |
Ludovic Courtès |
Subject: |
Re: Test failure in util-linux |
Date: |
Tue, 14 Apr 2015 11:59:46 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
address@hidden (Carlos Sánchez de La Lama) skribis:
>>> The system build fails during "check" phase of util-linux-2.25.2.
>>
>> Oh, OK. We could work around it, but since that requires a full
>> rebuild, we’ll have to schedule it for the next core update cycle.
>>
>> That said, 2.6.32 is really old, so we probably don’t want to invest too
>> much in that.
>
> Ok, I will try to do it myself in a proper "clean" to get hands dirty
> with package definitions. Then it can be included upstream if you find
> it appropiate.
Sounds good!
>>> 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)?
Thanks,
Ludo’.