From: Phil Beadling <phil@beadling.co.uk>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: scm_lreadr error on guix pull
Date: Mon, 23 Aug 2021 14:21:11 +0100 [thread overview]
Message-ID: <CAOvsyQsBoH26_VreRkaXMfheNVA8qvAK2LKipmp5orcdh1i4LA@mail.gmail.com> (raw)
In-Reply-To: <CAOvsyQtKyK20zM2rBWruttJaKd_roT81hNvX5g0EPPUamk+siw@mail.gmail.com>
Some more info from me - I've removed my local channel and reproduced using
only guix:
$ guix pull
Updating channel 'guix' from Git repository at '
https://git.savannah.gnu.org/git/guix.git'...
Building from this channel:
guix https://git.savannah.gnu.org/git/guix.git 6755408
building
/gnu/store/9g3qj7yicd7sc8312pmvbw6adyv8y877-module-import-compiled.drv...
|builder for
`/gnu/store/9g3qj7yicd7sc8312pmvbw6adyv8y877-module-import-compiled.drv'
failed with exit code 1
build of
/gnu/store/9g3qj7yicd7sc8312pmvbw6adyv8y877-module-import-compiled.drv
failed
View build log at
'/var/log/guix/drvs/9g/3qj7yicd7sc8312pmvbw6adyv8y877-module-import-compiled.drv.bz2'.
cannot build derivation
`/gnu/store/hp8l72b5pxfwys4x806pkl0apkzg9s4g-compute-guix-derivation.drv':
1 dependencies couldn't be built
guix pull: error: build of
`/gnu/store/hp8l72b5pxfwys4x806pkl0apkzg9s4g-compute-guix-derivation.drv'
failed
There's also a bit more info I forgot to include in the stdout.
I have tried to do a "guix pull --rollback" - that didn't seem to help.
On Mon, 23 Aug 2021 at 14:01, Phil Beadling <phil@beadling.co.uk> wrote:
> Thanks for your help Ricardo - see inline.
>
> On Mon, 23 Aug 2021 at 13:45, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>>
>>
>> I cannot reproduce this.
>>
>> Could you please provide the output of “guix describe”? What Guix
>> are you using after deleting ~/.config/guix?
>>
>> guix 6755408
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit: 675540892719387e1e4e76f097ff8e4ee4b559f7
>
> I also have a local guix channel but have no reason to think that is the
> issue at the moment.
>
> I can only reproduce this issue on a single user account. All the other
> accounts I've tried (on the same server) , report exactly the same commit
> from guix describe yet do not show the issue.
>
> When deleting the current profile, I end up using the same version
> anyway. Note I do have the guix repo anchored at
> 675540892719387e1e4e76f097ff8e4ee4b559f7 in the channel setup.
>
> /usr/local/bin/guix --version
> guix (GNU Guix) 675540892719387e1e4e76f097ff8e4ee4b559f7
> Copyright (C) 2021 the Guix authors
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
>
next prev parent reply other threads:[~2021-08-23 13:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 11:52 scm_lreadr error on guix pull Phil Beadling
2021-08-23 12:44 ` Ricardo Wurmus
2021-08-23 13:01 ` Phil Beadling
2021-08-23 13:21 ` Phil Beadling [this message]
2021-08-23 13:59 ` zimoun
2021-08-23 14:15 ` Phil Beadling
[not found] ` <CAOvsyQu+vogcL=gbeiCjJC8LZX2WNLpq42U6CEN681Yu0gQK-w@mail.gmail.com>
2021-08-23 17:18 ` zimoun
2021-08-23 17:52 ` Phil Beadling
2021-08-24 10:12 ` zimoun
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=CAOvsyQsBoH26_VreRkaXMfheNVA8qvAK2LKipmp5orcdh1i4LA@mail.gmail.com \
--to=phil@beadling.co.uk \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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).