From: John via <help-guix@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Fixing git permissions after sudo guix pull
Date: Sun, 1 Sep 2024 15:07:38 +0100 (GMT+01:00) [thread overview]
Message-ID: <f806d06e-0237-43e3-be27-3584ad650aaa@choffee.co.uk> (raw)
In-Reply-To: <9059FCAD-4F1B-4863-A496-56386B908A60@tobias.gr>
Hi Tobias,
Moving .cache/guix out the way seems to have fixed things. There was nothing in there that was not owned by me so the sudo was a bit of a red herring. Doing a git fsck on the old cache dir does show a broken pack file as you suggested so it's something getting corrupted which is slightly more worrying. Not sure there is any way to track down when that happened.
As a side note. Running "sudo guix pull" does not bail out with the error in the patch you showed so I'm not sure if there is something else going on there.
Thanks for your help
John
1 Sept 2024 13:51:50 Tobias Geerinckx-Rice <me@tobias.gr>:
> Hi John,
>
> I thought that any modern 'guix pull' would protect[0] itself from accidental sudoage. Perhaps the check's a little naive. Or there's some subtler effect of using sudo...
>
> How confident are you that the ownership is incorrect? The only "incorrect data check" error string I could find was in zlib, which would point to pack file corruption more than incorrect ownership.
>
> Guix's git checkouts are stashed in ~/.cache/guix/checkouts. As the name implies you can safely delete it or even the entire 'guix' directory, at the expense of subsequent downloads & computation.
>
> You could also rename it for later investigation, but I'm unable to volunteer for that myself. Don't feel obliged.
>
> [0]: https://git.savannah.gnu.org/cgit/guix.git/commit/guix/scripts/pull.scm?id=7c52cad0464175370c44bd4695e4c01a62b8268f
>
>
> Kind regards,
>
> T G-R
>
> Sent on the go. Excuse or enjoy my brevity.
prev parent reply other threads:[~2024-09-01 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-01 12:15 Fixing git permissions after sudo guix pull John
2024-09-01 12:51 ` Tobias Geerinckx-Rice
2024-09-01 14:07 ` John via [this message]
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=f806d06e-0237-43e3-be27-3584ad650aaa@choffee.co.uk \
--to=help-guix@gnu.org \
--cc=john@choffee.co.uk \
/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).