all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Zain Jabbar <zaijab2000@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 54969@debbugs.gnu.org
Subject: bug#54969: "activate.scm.drv" Empty and Live
Date: Sat, 16 Apr 2022 04:18:57 -1000	[thread overview]
Message-ID: <CAH+UbWTvOQQEy_1KY-hAJrWPDBOPVa2EOv9Vf6fHgGVz7s=u=w@mail.gmail.com> (raw)
In-Reply-To: <58290879a9a4bab95c58fd04ac84d77a9e2ad6ca.camel@telenet.be>

[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

Aloha Maxime Devos,

Your suggestion worked! I did the following but I'm not sure how much was
actually needed:

1. Use guix pull and guix system to switch to an older generation (I did
like -100)
2. Use guix gc
3. Run guix system again which remakes the files (like activate.scm as per
title)

This time guix system actually runs to completion. Mahalo nui iā ʻoe!

On Sat, Apr 16, 2022, 3:53 AM Maxime Devos <maximedevos@telenet.be> wrote:

> Zain Jabbar schreef op vr 15-04-2022 om 15:20 [-1000]:
> > Is it known why this could happen in the first place?
>
> I guess a power outage or the like.  Currently the guix daemon never
> calls 'sync' or the like (except possibly for the SQlite db), though
> maybe it should (at cost of some performance).
>
> > Is the only way to fix this to reinstall Guix?
>
> That's a way to do it, but there are less heavy-handed ways.  E.g.,
> maybe "guix gc --verify=repair" could be extended to delete objects
> that are broken (wrong hash) and aren't referenced? (long-term)
>
> For the short term, maybe do "guix gc", possibly some of the broken
> files are unused.
>
> Greetings,
> Maxime.
>

[-- Attachment #2: Type: text/html, Size: 1727 bytes --]

  reply	other threads:[~2022-04-16 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-16  1:20 bug#54969: "activate.scm.drv" Empty and Live Zain Jabbar
2022-04-16 13:52 ` Maxime Devos
2022-04-16 14:18   ` Zain Jabbar [this message]
2022-04-16 14:47     ` Maxime Devos

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH+UbWTvOQQEy_1KY-hAJrWPDBOPVa2EOv9Vf6fHgGVz7s=u=w@mail.gmail.com' \
    --to=zaijab2000@gmail.com \
    --cc=54969@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.