‘guix pull’ maintains Git clones under ~/.cache/guix/checkouts.
Probably the hardware issue led to a corrupt checkout there, hence the
error above. You fix that by running:
rm -rf ~/.cache/guix/checkouts
before running ‘guix pull’ again.
Hi Ludo,
Sory for not answering earlier. That helpe
‘guix pull’ maintains Git clones under ~/.cache/guix/checkouts.
Probably the hardware issue led to a corrupt checkout there, hence the
error above. You fix that by running:
rm -rf ~/.cache/guix/checkouts
before running ‘guix pull’ again.
Hi Ludo,
Sory for not answering earlier. That hel
Hi,
On Wed, 22 Apr 2020 at 23:08, Ludovic Courtès wrote:
> ‘guix pull’ maintains Git clones under ~/.cache/guix/checkouts.
What is the naming scheme? Especially how is computed the hash of the
folder name?
And not relevant considering this bug: could the first commit after
the big overhaul (in
Hi Mayeul,
Mayeul Cantan skribis:
> I was running guix pull, when a short-cirguit in my power supply cable
> turned my old laptop off.
>
> Having fixed the hardware issue, I am left with the following software
> problem when running `guix pull` on my user session:
>
>> guix pull: error: Git erro
Le 22 avril 2020 09:21:38 GMT-04:00, Mayeul Cantan a
écrit :
>Hello there,
>
>I was running guix pull, when a short-cirguit in my power supply cable
>turned my old laptop off.
>
>Having fixed the hardware issue, I am left with the following software
>problem when running `guix pull` on my user
Hello there,
I was running guix pull, when a short-cirguit in my power supply cable
turned my old laptop off.
Having fixed the hardware issue, I am left with the following software
problem when running `guix pull` on my user session:
guix pull: error: Git error: object not found - no match
