bug-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#33082: guix pull resulted in an error: compute-guix-derivation


From: Joshua Branson
Subject: bug#33082: guix pull resulted in an error: compute-guix-derivation
Date: Tue, 30 Oct 2018 11:15:08 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)

Gábor Boskovits <address@hidden> writes:

> Hello Joshua,
>
> Joshua Branson <address@hidden> ezt írta (időpont: 2018. okt.
> 30., K, 13:44):
>>
>> Gábor Boskovits <address@hidden> writes:
>>
>> > Joshua Branson <address@hidden> ezt írta (időpont: 2018. okt. 29., H 
>> > 15:54):
>> >
>> >  address@hidden (Ludovic Courtès) writes:
>> >
>> >  > Hello,
>> >  >
>> >
>> >  I was able to update successfully.  This bug seems like a duplicate of
>> >  python 2 not deterministic.  Someone ought to close this bug report.
>> >
>> > I believe this is not the case, usually non deterministic means the build 
>> > is not reproducible, while this is a
>> > non-deterministic test failure. I would suggest
>> > keeping this bug open, if I am right, maybe renaming to non-deterministic 
>> > test failure in python2. What do you think?
>>
>> Fair enough.  Since I made the bug report, then I should try to build it
>> again and see what happens.
>>
>
> Thanks for having a look, please make sure to use guix build -K, so
> that the failed build results are retained.
> If you can't trigger the failure, then I will try to do this later.

I was able to build this successfully:

guix build -K /gnu/store/qpvqn6ff2lmfq74ff3i9pz5hrb01p9hw-python2-2.7.14.drv


Collecting setuptools
Collecting pip
Installing collected packages: setuptools, pip
Successfully installed pip-9.0.1 setuptools-28.8.0
phase `install' succeeded after 32.6 seconds
starting phase `move-tk-inter'
phase `move-tk-inter' succeeded after 0.2 seconds
starting phase `remove-tests'
phase `remove-tests' succeeded after 0.8 seconds
starting phase `patch-shebangs'
phase `patch-shebangs' succeeded after 0.0 seconds
starting phase `make-libraries-writable'
phase `make-libraries-writable' succeeded after 0.1 seconds
starting phase `strip'
stripping binaries in 
"/gnu/store/l7164sj4k77c4bwy9mrqq9d96bxiz4kw-python2-2.7.14/lib" with "strip" 
and flags ("--strip-debug" "--enable-deterministic-archives")
stripping binaries in 
"/gnu/store/l7164sj4k77c4bwy9mrqq9d96bxiz4kw-python2-2.7.14/bin" with "strip" 
and flags ("--strip-debug" "--enable-deterministic-archives")
stripping binaries in 
"/gnu/store/z0r8jiimjgdg2sl3h9ad9z1v1i95752v-python2-2.7.14-tk/lib" with 
"strip" and flags ("--strip-debug" "--enable-deterministic-archives")
phase `strip' succeeded after 2.9 seconds
starting phase `validate-runpath'
validating RUNPATH of 64 binaries in 
"/gnu/store/l7164sj4k77c4bwy9mrqq9d96bxiz4kw-python2-2.7.14/lib"...
validating RUNPATH of 1 binaries in 
"/gnu/store/l7164sj4k77c4bwy9mrqq9d96bxiz4kw-python2-2.7.14/bin"...
validating RUNPATH of 1 binaries in 
"/gnu/store/z0r8jiimjgdg2sl3h9ad9z1v1i95752v-python2-2.7.14-tk/lib"...
phase `validate-runpath' succeeded after 1.1 seconds
starting phase `validate-documentation-location'
phase `validate-documentation-location' succeeded after 0.0 seconds
starting phase `delete-info-dir-file'
phase `delete-info-dir-file' succeeded after 0.0 seconds
starting phase `patch-dot-desktop-files'
phase `patch-dot-desktop-files' succeeded after 0.0 seconds
starting phase `install-license-files'
installing 1 license files
phase `install-license-files' succeeded after 0.0 seconds
starting phase `reset-gzip-timestamps'
phase `reset-gzip-timestamps' succeeded after 0.1 seconds
starting phase `compress-documentation'
compressing documentation in 
'/gnu/store/l7164sj4k77c4bwy9mrqq9d96bxiz4kw-python2-2.7.14/share/man' with 
"gzip" and flags ("--best" "--no-name")
phase `compress-documentation' succeeded after 0.1 seconds
successfully built 
/gnu/store/qpvqn6ff2lmfq74ff3i9pz5hrb01p9hw-python2-2.7.14.drv
/gnu/store/l7164sj4k77c4bwy9mrqq9d96bxiz4kw-python2-2.7.14
/gnu/store/z0r8jiimjgdg2sl3h9ad9z1v1i95752v-python2-2.7.14-tk


I suppose now we can close this bug report, since I can't reproduce the
error?

Thanks

>
> Best regards,
> g_bor





reply via email to

[Prev in Thread] Current Thread [Next in Thread]