From: Tim Lee <progscriptclone@gmail.com>
To: help-guix@gnu.org
Subject: 'guix deploy' installs old version of Guix on Digital Ocean
Date: Sat, 27 Mar 2021 02:59:36 +0800 [thread overview]
Message-ID: <20210326185936.vnhhnu6m3zny56es@home-guest> (raw)
I am following this article to manage my Digital Ocean servers using
'guix deploy':
https://guix.gnu.org/blog/2019/managing-servers-with-gnu-guix-a-tutorial/
However, I notice that the Digital Ocean deployment actually installs
Guix version 1.0.1 (May 2019) instead of the latest version — 1.2.0
(November 2020).
I looked into the source code and found that gnu/machine/digital-ocean.scm
is outdated:
https://github.com/guix-mirror/guix/blob/v1.2.0/gnu/machine/digital-ocean.scm#L198
Is it safe to deploy an old version of Guix, considering the massive
improvements that have taken place over 18 months between May 2019 and
November 2020?
next reply other threads:[~2021-03-26 20:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 18:59 Tim Lee [this message]
2021-03-26 21:54 ` 'guix deploy' installs old version of Guix on Digital Ocean Vincent Legoll
2021-03-26 22:25 ` Tim Lee
2021-03-26 22:55 ` Tim Lee
2021-03-26 23:01 ` Leo Famulari
2021-03-26 23:13 ` Tim Lee
2021-03-26 23:46 ` Leo Famulari
2021-03-26 23:00 ` Leo Famulari
2021-03-27 15:08 ` Tim Lee
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=20210326185936.vnhhnu6m3zny56es@home-guest \
--to=progscriptclone@gmail.com \
--cc=help-guix@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.
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).