From: Guillaume Le Vaillant <glv@posteo.net>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: Roman Riabenko <roman@riabenko.com>, 66169@debbugs.gnu.org
Subject: bug#66169: guix reconfigure error no match for id 4f35ff1275e05be31f5d41464ccf147e9dbfd016
Date: Sun, 24 Sep 2023 09:22:49 +0000 [thread overview]
Message-ID: <87h6njrkgv.fsf@kitej> (raw)
In-Reply-To: <4d6bf9b098374bcb1de0fc46347378dc57b4c043.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1838 bytes --]
Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:
> Am Sonntag, dem 24.09.2023 um 08:49 +0000 schrieb Guillaume Le
> Vaillant:
>> Liliana Marie Prikler <liliana.prikler@gmail.com> skribis:
>>
>> > Am Samstag, dem 23.09.2023 um 22:02 +0300 schrieb Roman Riabenko:
>> > > 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.
>> > Experiencing the same for commit
>> > 35fd25af9bbcce84908101a9f487ba106a8d6df7. I would hazard a guess
>> > that it's due to them being merge commits. Interestingly,
>> > allow-downgrades does not have an effect on this message.
>> >
>> > Cheers
>>
>> I reconfigured two machines using commit
>> 4f35ff1275e05be31f5d41464ccf147e9dbfd016, and it succeeded on both
>> machines, I didn't get this "no match for id" issue.
>> That's strange...
> Do you have provenance tracking on your machines (the default)?
Yes. I use an additional channel, not only the "guix" default channel.
Maybe that makes a difference...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2023-09-24 9:27 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 [this message]
2023-09-25 8:30 ` Paul Szenher
2023-09-24 9:16 ` Liliana Marie Prikler
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=87h6njrkgv.fsf@kitej \
--to=glv@posteo.net \
--cc=66169@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--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).