unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Jesse Gibbons <jgibbons2357@gmail.com>, melon <shack@muto.ca>,
	37374@debbugs.gnu.org
Subject: bug#37374: "Guix is too old and cannot be upgraded" (guix package -u)
Date: Wed, 11 Sep 2019 23:09:13 +0200	[thread overview]
Message-ID: <87sgp2o806.fsf@gnu.org> (raw)
In-Reply-To: <87woefpb99.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 11 Sep 2019 09:01:22 +0200")

Hello,

Ricardo Wurmus <rekado@elephly.net> skribis:

>> Wow, now I want to keep guix up-to-date all the time. How long has it
>> been since you pulled/upgraded guix?
>
> There’s no need to worry about that.  The mechanism to upgrade Guix has
> changed significantly over the past years and has since stabilized.
> This error will usually only hit you if you’re using a *much* older
> Guix that predates the changes how “guix pull” works.

Specifically, the message “Guix is too old and cannot be upgraded”
appears when you’re running ‘guix pull’ from Guix before 0.15.0,
released in July 2018.  (That seemed like prehistory to me but I realize
it’s only a bit more than one year old.)

But like Ricardo wrote, such problems are unlikely to show up again
because ‘guix pull’ since 0.15.0 is designed to handle all sorts of
bumps into future Guix revisions.

Anyway, the simplest option for now, melon, may be to remove your
current Guix installation and install 1.0 instead.

Ludo’.

  reply	other threads:[~2019-09-11 21:10 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
2019-09-11  7:01   ` Ricardo Wurmus
2019-09-11 21:09     ` Ludovic Courtès [this message]
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=87sgp2o806.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=37374@debbugs.gnu.org \
    --cc=jgibbons2357@gmail.com \
    --cc=rekado@elephly.net \
    --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).