[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#31843: guix pull corrupted current guix
From: |
Julien Lepiller |
Subject: |
bug#31843: guix pull corrupted current guix |
Date: |
Fri, 15 Jun 2018 13:25:43 +0200 |
User-agent: |
Roundcube Webmail/1.3.6 |
Hi, running guix pull this morning corrupted my current guix command.
I am running on guixsd. Because I don't have a lot of memory, I sent a
generation of .config/guix/current to the server with:
guix archive --export -r `readlink -f .config/guix/current` | ssh
machine guix archive --import
Then, I created a link from /var/guix/gcroots to the
.config/guix/current, and from that to the store item that was
transferred.
This morning, I tried to run guix pull to see how far it would go (and
if I could download some parts from hydra or berlin). As expected, it
ran out of memory, but left my store in a state where the guix command
linked to from .config/guix/current only contains garbage. Attached is
the output of "guix pull --cores=1" on that machine that lead to the
bug, and the new content of the guix command.
The corrupted file is from a store item that was present (and valid)
before I ran guix pull, so I thought it was impossible for guix to
modify it.
I think a fix is to remove .config/guix/current, run an older version of
guix to try and repair the store with guix gc, and send the guix package
from my other machine again. I haven't tried that yet, as my broken
machine still mostly works, although I doubt it can boot now. Since I
didn't try to fix anything, I can give more details if you want. The
guix I used to pull is from commit
85d79a79e4b721e24cdfb11a90beef6d566c499a, and the pulled commit is
0017e55f892828f7a4d29a50f06e5146270ab8cb.
guix-command
Description: Text document
guix-pull.log
Description: Text document
- bug#31843: guix pull corrupted current guix,
Julien Lepiller <=