unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Joey Dumont <joey.dumont@gmail.com>, help-guix@gnu.org
Subject: Re: Delete all previous derivations
Date: Fri, 29 Apr 2022 18:27:28 +0200	[thread overview]
Message-ID: <87pmkzc0sv.fsf@gmail.com> (raw)
In-Reply-To: <CAB6-_idH_=O+rs2ETmQ+TpWKiWqtMKU0fJKop=rrWQxiak4Lvw@mail.gmail.com>

Hi,

On Fri, 08 Apr 2022 at 23:14, Joey Dumont <joey.dumont@gmail.com> wrote:

> I am using guix on Arch Linux, installed through the AUR package, but with
> a custom store directory: --with-store-dir=/cvmfs/soft.valandil.ca/2022.03.
> I was running the daemon with options:
>
> # /etc/systemd/system/guix-daemon.service.d/override.conf
> [Service]
> ExecStart=
> ExecStart=/usr/bin/guix-daemon --build-users-group=guixbuild
> --gc-keep-outputs=yes --gc-keep-derivations=yes
>
> I have since updated my guix install to point to a new store: /cvmfs/
> soft.valandil.ca/2022.04, but I keep getting errors when running guix pull:

Hum, interesting setup… but then Guix will be confused, I guess.

> $ guix pull
> ;;; WARNING: loading compiled file /usr/lib/guile/2.2/site-ccache/gnutls.go
> failed:
> ;;; In procedure load-thunk-from-file: Invalid argument
> ;;; WARNING: loading compiled file /usr/lib/guile/2.2/site-ccache/gnutls.go
> failed:
> ;;; In procedure load-thunk-from-file: Invalid argument
> Updating channel 'guix-hpc' from Git repository at '
> https://gitlab.inria.fr/guix-hpc/guix-hpc'...
> Updating channel 'guix' from Git repository at '
> https://git.savannah.gnu.org/git/guix.git'...
> Authenticating channel 'guix', commits 9edb3f6 to 1d4f2cd (23 new
> commits)...
> Building from these channels:
>   guix      https://git.savannah.gnu.org/git/guix.git 1d4f2cd
>   guix-hpc  https://gitlab.inria.fr/guix-hpc/guix-hpc de22a12
> guix pull: error: derivation `/cvmfs/
> soft.valandil.ca/2022.03/compat/x86_64/linux/pf4z6hc1f9bwddsravnlacnb2i8p9xyl-guile-3.0.2.tar.xz.drv'
> has incorrect output `/cvmfs/
> soft.valandil.ca/2022.04/compat/x86_64/linux/92ip5misld973bsm73hfazwmd4n9d58z-guile-3.0.2.tar.xz',
> should be `/cvmfs/
> soft.valandil.ca/2022.03/compat/x86_64/linux/9gc2alnhkrilqdch2xzjg0vq9b44is43-guile-3.0.2.tar.xz
> '

Ah, Guix is really confused. :-)

> I tried stracing the guix pull, and deleted all cache entries I could,
> ~/.cache/{guile,guix}, and the previous store, but the error persists.
> Where is that derivation stored so that it can be compared against the new
> derivation? How can I delete it?

IIUC, you have 2 stores.  It means now you have 2 SQLite databases and
so on.  Well, I do not know how it can work.

You pulled with the old store.  So the current guix command points to an
item to this old store.  To change the store location
(--with-store-dir), you have recompiled Guix, right?

Then, did you run

    ./pre-inst-env guix pull -p ~/.config/guix/current
    ~/.config/guix/current/bin/guix pull

?


Cheers,
simon


  reply	other threads:[~2022-04-29 16:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-09  3:14 Delete all previous derivations Joey Dumont
2022-04-29 16:27 ` zimoun [this message]
2022-05-20  1:14   ` Joey Dumont
2022-05-20  7:15     ` 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=87pmkzc0sv.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=joey.dumont@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).