From: Paul Szenher <88paul98@gmail.com>
To: 66169@debbugs.gnu.org
Subject: bug#66169: guix reconfigure error no match for id 4f35ff1275e05be31f5d41464ccf147e9dbfd016
Date: Mon, 25 Sep 2023 04:30:34 -0400 [thread overview]
Message-ID: <fc89b990-15cd-216e-b211-c78563c9c994@gmail.com> (raw)
In-Reply-To: <87h6njrkgv.fsf@kitej>
On 9/24/23 5:22 AM, Guillaume Le Vaillant wrote:
> 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...
Also reporting similar issues on a Guix machine with multiple channels.
In my case, I have a local 'file://...' channel that I use for
development, and have found that the following sequence of actions will
consistently exhibit the above behavior on guix master:
1. Commit update to local channel git
2. guix pull
3. sudo guix system reconfigure
The issue is resolved by removal of the root user's guix cache in
/root/.cache/guix (forcing a full fetch during system reconfigure), but
repeating the above steps will cause the issue to reoccur.
I suspect it might have to do with the recent changes made to the
'reference-available?' function in
6d33c1f8061e86d63ab5c9ec75df9c58130c7264 (though it's not entirely clear
why that change would cause this failure).
After downgrading my "guix" channel to
f45c0c82289d409b4fac00464ea8b323839ba53f (the commit immediately prior
to the above change) I am again able to receive changes from my local
channel without issue.
next prev parent reply other threads:[~2023-09-26 22:14 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 [this message]
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=fc89b990-15cd-216e-b211-c78563c9c994@gmail.com \
--to=88paul98@gmail.com \
--cc=66169@debbugs.gnu.org \
/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).