GNU bug report logs -
#68532
git-crypt can fail after guix gc
Previous Next
To reply to this bug, email your comments to 68532 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#68532
; Package
guix
.
(Wed, 17 Jan 2024 15:47:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
TakeV <takev <at> disroot.org>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Wed, 17 Jan 2024 15:47:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
I set up a git repo which uses git-crypt a while back, however it seems
to have broken in the time between then and now.
Looking into how git-crypt seems to handle things; running the initial
init causes the full path to the git-crypt binary to be written to the
git config file (.git/config) as a filter.
If one has created a repo using git-crypt, and some time later runs guix
gc, then the old path to the git-crypt binary likely will be deleted,
causing git-crypt to break, as it is unable to locate the binary.
One workaround could be running git-crypt in a shell, and registering it
as a garbage collector root so that the original git-crypt install is
preserved, but that seems like it would not be an optimal long term fix.
Updating the config file by hand also seems to fix the issue, though
that route is similarly a short term fix.
[OpenPGP_signature (application/pgp-signature, attachment)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#68532
; Package
guix
.
(Thu, 24 Apr 2025 14:18:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 68532 <at> debbugs.gnu.org (full text, mbox):
On Wed, Jan 17, 2024 at 10:47 AM TakeV via Bug reports for GNU Guix
<bug-guix <at> gnu.org> wrote:
>
> I set up a git repo which uses git-crypt a while back, however it seems
> to have broken in the time between then and now.
>
> Looking into how git-crypt seems to handle things; running the initial
> init causes the full path to the git-crypt binary to be written to the
> git config file (.git/config) as a filter.
>
> If one has created a repo using git-crypt, and some time later runs guix
> gc, then the old path to the git-crypt binary likely will be deleted,
> causing git-crypt to break, as it is unable to locate the binary.
>
> One workaround could be running git-crypt in a shell, and registering it
> as a garbage collector root so that the original git-crypt install is
> preserved, but that seems like it would not be an optimal long term fix.
> Updating the config file by hand also seems to fix the issue, though
> that route is similarly a short term fix.
I am not seeing any changes or updates to the git-crypt package since
this issue was opened, but I am also not seeing the full path to the
git-crypt binary when I "git init" and "git-crypt init" a new repo:
$ cat .git/config
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[filter "git-crypt"]
smudge = \"git-crypt\" smudge
clean = \"git-crypt\" clean
required = true
[diff "git-crypt"]
textconv = \"git-crypt\" diff
This bug report was last modified 52 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.