unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Phil Beadling <phil@beadling.co.uk>
To: zimoun <zimon.toutoune@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: scm_lreadr error on guix pull
Date: Mon, 23 Aug 2021 15:15:37 +0100	[thread overview]
Message-ID: <CAOvsyQsPkM8r31mNjc3SMxpTQ8iG5-Hmc4gJPoVubP5a6oWJaQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ3okZ0khQrviNeVwoQUrHcJFnwa4V=w7rc8zA-Wj1wYOuEq5w@mail.gmail.com>

On Mon, 23 Aug 2021 at 14:59, zimoun <zimon.toutoune@gmail.com> wrote:

>
> This commit is from May 2021.  So it is weird that you pull this commit.
>

Yep - I keep all my accounts in lockstep and move them every few months -
it has been a while since I've done this, but the commit id shouldn't
matter - I should be able to set that to any commit id and have it work.
The other accounts are locked to the same commit id and they have no issue.

Also if I force to current head it still errors (see below).

I've also tried clearing the ~/.cache/guix directory and deleting the
/var/guix/profiles/per-user/<USERNAME> directory - no luck, alas.

Is there anyway to obliterate Guix setup for this one user account and then
start from scratch.  Given that all other users on the same server don't
see this problem, that's probably the nuclear option?  There's nothing
precious in terms of rollbacks that I couldn't afford to lose - espically
given the rollbacks seem to be broken too.


$ guix pull --commit=f04883d0ba8ddd3977b18ccfc281a5de64bd2e1e
Updating channel 'guix' from Git repository at '
https://git.savannah.gnu.org/git/guix.git'...
Authenticating channel 'guix', commits 9edb3f6 to f04883d (4,030 new
commits)...
Building from this channel:
  guix      https://git.savannah.gnu.org/git/guix.git   f04883d
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
building /gnu/store/pq4rnyd4bnal3hpqihzgl5f78rxjh364-module-import.drv...
building /gnu/store/xvnwq3i51ifnz8w02a6zai3k0p8ak7ka-module-import.drv...
building
/gnu/store/8yyhppqch35nshc4svgn8kmf06sawazd-module-import-compiled.drv...
|builder for
`/gnu/store/8yyhppqch35nshc4svgn8kmf06sawazd-module-import-compiled.drv'
failed with exit code 1
build of
/gnu/store/8yyhppqch35nshc4svgn8kmf06sawazd-module-import-compiled.drv
failed
View build log at
'/var/log/guix/drvs/8y/yhppqch35nshc4svgn8kmf06sawazd-module-import-compiled.drv.bz2'.
cannot build derivation
`/gnu/store/lfxvnnmbcdwr4si80hmmr8bryz6qk2d9-compute-guix-derivation.drv':
1 dependencies couldn't be built
guix pull: error: build of
`/gnu/store/lfxvnnmbcdwr4si80hmmr8bryz6qk2d9-compute-guix-derivation.drv'
failed
$

  reply	other threads:[~2021-08-23 14:16 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
2021-08-23 13:59       ` zimoun
2021-08-23 14:15         ` Phil Beadling [this message]
     [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=CAOvsyQsPkM8r31mNjc3SMxpTQ8iG5-Hmc4gJPoVubP5a6oWJaQ@mail.gmail.com \
    --to=phil@beadling.co.uk \
    --cc=help-guix@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).