From: Jesse Gibbons <jgibbons2357@gmail.com>
To: melon <shack@muto.ca>, 37374@debbugs.gnu.org
Subject: bug#37374: "Guix is too old and cannot be upgraded" (guix package -u)
Date: Tue, 10 Sep 2019 19:29:30 -0600 [thread overview]
Message-ID: <24bccfebf40e114498af09d86a1032a2cd82075c.camel@gmail.com> (raw)
In-Reply-To: <87mufb3epg.fsf@muto.ca>
On Tue, 2019-09-10 at 17:37 -0600, melon wrote:
> I was attempting to upgrade my Guix (binary, on Linux Mint)
> installation
> today using the 'guix package pull && guix package -u' commands, and
> Guix outputted the following error:
>
> ERROR: In procedure raise:
> Wrong type (expecting exact integer): #<condition &message [message:
> "Guix is too old and cannot be upgraded"] 7528ac0>
> guix pull: error: You found a bug: the program
> '/gnu/store/y1kqj5ikxx9niyz2zx1gbikspi2xfmi4-compute-guix-derivation'
> failed to compute the derivation for Guix (version:
> "7e143375d3649f3c0bd4c13958b26c086f364647"; system: "x86_64-linux";
> host version: "aa4818c33b6b2fd8d602ee93a2f53005d9472f41"; pull-
> version: 0).
> Please report it by email to <bug-guix@gnu.org>.
>
> I searched the Web and mailing list archives for this error but could
> not find anything. Maybe I used the wrong keywords.
>
> Is there any way I can perform a "manual upgrade" to a newer Guix
> version?
>
Wow, now I want to keep guix up-to-date all the time. How long has it
been since you pulled/upgraded guix?
The first thing I thought of is manually remove the guix binary run
install script. But that might get complicated.
I think you can look at the git repo on savannah and pull a few commits
after your current commit (run "guix describe" to get the commit, then
"guix pull --commit=COMMIT" where COMMIT is about a hundred commits
after your current commit), repeating until "guix pull" brings guix
fully up-to-date.
next prev parent reply other threads:[~2019-09-11 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 23:37 bug#37374: "Guix is too old and cannot be upgraded" (guix package -u) melon
2019-09-11 1:29 ` Jesse Gibbons [this message]
2019-09-11 7:01 ` Ricardo Wurmus
2019-09-11 21:09 ` Ludovic Courtès
2019-09-11 5:46 ` pelzflorian (Florian Pelz)
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=24bccfebf40e114498af09d86a1032a2cd82075c.camel@gmail.com \
--to=jgibbons2357@gmail.com \
--cc=37374@debbugs.gnu.org \
--cc=shack@muto.ca \
/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).