[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Fixing git permissions after sudo guix pull
From: |
John |
Subject: |
Re: Fixing git permissions after sudo guix pull |
Date: |
Sun, 1 Sep 2024 15:07:38 +0100 (GMT+01:00) |
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.