emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#66169: closed (merge commits may harm your cache maybe?)


From: GNU bug Tracking System
Subject: bug#66169: closed (merge commits may harm your cache maybe?)
Date: Wed, 11 Oct 2023 14:32:02 +0000

Your message dated Wed, 11 Oct 2023 16:12:23 +0200
with message-id <875y3dtfi0.fsf@gmail.com>
and subject line Re: bug#66169: guix reconfigure error no match for id 
4f35ff1275e05be31f5d41464ccf147e9dbfd016
has caused the debbugs.gnu.org bug report #66169,
regarding merge commits may harm your cache maybe?
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
66169: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66169
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: guix reconfigure error no match for id 4f35ff1275e05be31f5d41464ccf147e9dbfd016 Date: Sat, 23 Sep 2023 22:02:47 +0300 User-agent: Evolution 3.46.4
I am trying to upgrade my guix systems. I ran guix pull and now I am
trying to run guix system reconfigure. It failed on two different
machines with the same backtrace. Please see the full backtrace
attached. The error message from it:

ice-9/boot-9.scm:1685:16: In procedure raise-exception:
Git error: object not found - no match for id
(4f35ff1275e05be31f5d41464ccf147e9dbfd016)


$ guix describe
Generation 28   Sep 23 2023 19:30:36    (current)
  guix 4f35ff1
    repository URL: https://git.savannah.gnu.org/git/guix.git
    branch: master
    commit: 4f35ff1275e05be31f5d41464ccf147e9dbfd016

Considering that I experience it on two guix machines with different
system configurations, I assume that there is some bug somewhere.

Roman

Attachment: backtrace.txt
Description: Text document

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message --- Subject: Re: bug#66169: guix reconfigure error no match for id 4f35ff1275e05be31f5d41464ccf147e9dbfd016 Date: Wed, 11 Oct 2023 16:12:23 +0200
Hi,

On Mon, 25 Sep 2023 at 12:25, Simon Tournier <zimon.toutoune@gmail.com> wrote:

> Well, I guess it is now fixed by
> 94f3831e5bb1e04eeb3a0e7d31a0675208ce6f4c.

Closing.

Let me know if another discrepancy is around.

Cheers,
simon


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]