GNU bug report logs - #63122
guix refresh wrote the wrong version number

Previous Next

To reply to this bug, email your comments to 63122 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Jack Hill <jackhill <at> jackhill.us>
To: bug-guix <at> gnu.org
Subject: guix refresh wrote the wrong version number
Date: Thu, 27 Apr 2023 11:36:56 -0400 (EDT)

Hi Guix,

While working on the wlroots and sway update [0], I noticed the following 
odd behavior with `guix refresh`:

The problem occurred when using `guix refresh` to update sway. A plain 
`guix refresh sway` reported correctly that sway could be updated to 
1.8.1. However, when I ran `guix refresh -u sway`, the version written to 
the package definition way 1.8.1.1. However the hash was correct for 
1.8.1. Of course building the source for version 1.8.1.1 failed because 
the corresponding tag couldn't be found (and it wasn't yet in a 
content-addressed mirror). After correcting the version everything worked 
as expected.

I did this all with a pre-inst-env guix at commit 
8093c6ba21c51efe901ba98ce698c545bf13dcd0.

Best,
Jack

[0] https://issues.guix.gnu.org/63085

Message #8 received at 63122 <at> debbugs.gnu.org (full text, mbox):

From: "J. Sims" <jtsims <at> protonmail.com>
To: "63122 <at> debbugs.gnu.org" <63122 <at> debbugs.gnu.org>
Subject: re: guix refresh wrote the wrong version number
Date: Thu, 27 Apr 2023 20:09:00 +0000

Just wanted to confirm I've seen exactly the same behavior on a personal project in my personal Guix channel - an extra ".1" was written at the end of a version number ending in ".1" while everything else worked fine.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.