From: Kyle Andrews <kyle@posteo.net>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Maxime Devos" <maximedevos@telenet.be>,
55709@debbugs.gnu.org
Subject: bug#55709: R texinfo documents are not showing up for me
Date: Sat, 04 Jun 2022 23:29:26 +0000 [thread overview]
Message-ID: <87leucngdq.fsf@posteo.net> (raw)
In-Reply-To: <1866a29e035be8606f940de34228ab562bb935c5.camel@ist.tugraz.at>
I had a really hard time getting ~guix gc --verify=contents,repair~ to
actually fix the problem and get commands like emacs to run.
Nothing worked until I mounted /gnu/store as read write and removed the
zeroed file completely for that particular gtk+3.24.30 folder, removed
the ~guix/store/.links~ folder, and then finally reran the ~guix gc ...~
command. That was after doing a fsck as well.
Hat tip to Tobias for spending a good chunk of saturday helping me
through this. He though this might be related to issue 50121 after I
referred him to it.
Cheers,
Kyle
Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> writes:
> Am Dienstag, dem 31.05.2022 um 10:37 +0200 schrieb Maxime Devos:
>> (Is there a method to verify and repair a _single_ store item instead
>> of the whole store?).
> I think the syntax for that'd be ‘[sudo] guix build --repair
> STORE_ITEM’.
>
> Cheers
next prev parent reply other threads:[~2022-06-04 23:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 15:48 bug#55709: R texinfo documents are not showing up for me Kyle Andrews
2022-05-29 22:37 ` Ludovic Courtès
2022-05-31 0:35 ` Kyle Andrews
2022-05-31 8:37 ` Maxime Devos
2022-06-02 6:12 ` Liliana Marie Prikler
2022-06-04 23:29 ` Kyle Andrews [this message]
2022-05-31 9:37 ` Ludovic Courtès
2022-06-02 0:42 ` Kyle Andrews
2022-06-02 13:39 ` Ludovic Courtès
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=87leucngdq.fsf@posteo.net \
--to=kyle@posteo.net \
--cc=55709@debbugs.gnu.org \
--cc=liliana.prikler@ist.tugraz.at \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).