guix refresh wrote the wrong version number

  • Open
  • quality assurance status badge
Details
2 participants
  • Jack Hill
  • J. Sims
Owner
unassigned
Submitted by
Jack Hill
Severity
normal
J
J
Jack Hill wrote on 27 Apr 2023 17:36
(address . bug-guix@gnu.org)
alpine.DEB.2.21.2304271110310.331@marsh.hcoop.net
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

J
J
J. Sims wrote on 27 Apr 2023 22:09
(name . 63122@debbugs.gnu.org)(address . 63122@debbugs.gnu.org)
9MBzQZYcooBPAt8nTWHAMgNjV1JpriU7AlpNs2jYODxF3GZoGYipAP82RVXW59KHR6peKanaNiqVBahV7B9sRJ33JU5pJAc9wqhpZItKWuI=@protonmail.com
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.
?