unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Vincent Legoll <vincent.legoll@gmail.com>
To: help-guix <help-guix@gnu.org>
Subject: Re: 'guix deploy' installs old version of Guix on Digital Ocean
Date: Fri, 26 Mar 2021 22:54:00 +0100	[thread overview]
Message-ID: <CAEwRq=rYChUuboAVYi65t=RmMXhpqsrfG5U11jw2V-LnhNB9cA@mail.gmail.com> (raw)
In-Reply-To: <20210326185936.vnhhnu6m3zny56es@home-guest>

On Fri, Mar 26, 2021 at 9:55 PM Tim Lee <progscriptclone@gmail.com> wrote:
> 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

Heh, there's a lot of infection happening this evening (see the other
thread from ilmu)
And now I see where his script variant may be coming from, will the
infection rate be
higher ?

OK now, COVID-related jokes asides, you're right this is outdated.

You could try with just updating the URLs to guix binary tarballs and
tell us if this
still works, or even contribute by sending a patch fixing it.

This should be straightforward.

Contributing doc here:
https://guix.gnu.org/manual/en/html_node/Contributing.html#Contributing

Tchuss

--
Vincent Legoll


  reply	other threads:[~2021-03-26 21:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26 18:59 'guix deploy' installs old version of Guix on Digital Ocean Tim Lee
2021-03-26 21:54 ` Vincent Legoll [this message]
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='CAEwRq=rYChUuboAVYi65t=RmMXhpqsrfG5U11jw2V-LnhNB9cA@mail.gmail.com' \
    --to=vincent.legoll@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).