From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Roman Riabenko <roman@riabenko.com>, 66169@debbugs.gnu.org
Cc: Guillaume Le Vaillant <glv@posteo.net>
Subject: bug#66169: guix reconfigure error no match for id 4f35ff1275e05be31f5d41464ccf147e9dbfd016
Date: Sun, 24 Sep 2023 11:16:57 +0200 [thread overview]
Message-ID: <55c9e517e9d10fb8ac17b17ffebf14f1fff66a29.camel@gmail.com> (raw)
In-Reply-To: <2e78ea3a25d4da00c841c8dd35f0e533700bf659.camel@gmail.com>
Am Sonntag, dem 24.09.2023 um 10:37 +0200 schrieb Liliana Marie
Prikler:
> Am Samstag, dem 23.09.2023 um 22:02 +0300 schrieb Roman Riabenko:
> > ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> > Git error: object not found - no match for id
> > (4f35ff1275e05be31f5d41464ccf147e9dbfd016)
> Experiencing the same for commit
> 35fd25af9bbcce84908101a9f487ba106a8d6df7.
Am Sonntag, dem 24.09.2023 um 08:49 +0000 schrieb Guillaume Le
Vaillant:
> I reconfigured two machines using commit
> 4f35ff1275e05be31f5d41464ccf147e9dbfd016, and it succeeded on both
> machines[.]
I now have a workaround that looks quite odd. If you
$ sudo rm -rf /root/.cache/guix
guix system will rerun the indexing and thus pick up the new commits.
I will dub this "advanced cache invalidation" since it appears as
though we are looking up commits in the wrong cache.
Cheers
next prev parent reply other threads:[~2023-09-24 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 19:02 bug#66169: guix reconfigure error no match for id 4f35ff1275e05be31f5d41464ccf147e9dbfd016 Roman Riabenko via Bug reports for GNU Guix
2023-09-24 8:37 ` Liliana Marie Prikler
2023-09-24 8:49 ` Guillaume Le Vaillant
2023-09-24 8:56 ` Liliana Marie Prikler
2023-09-24 9:22 ` Guillaume Le Vaillant
2023-09-25 8:30 ` Paul Szenher
2023-09-24 9:16 ` Liliana Marie Prikler [this message]
2023-09-25 10:25 ` Simon Tournier
2023-10-11 14:12 ` Simon Tournier
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=55c9e517e9d10fb8ac17b17ffebf14f1fff66a29.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=66169@debbugs.gnu.org \
--cc=glv@posteo.net \
--cc=roman@riabenko.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).