From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Guix minor version update?
Date: Thu, 23 Jan 2020 16:42:31 +0100 [thread overview]
Message-ID: <87ftg6qivs.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ1dz6dQZ04wDbxCKLbuhWfQ9wmN8DbjydwVZ_g5cB3qiQ@mail.gmail.com> (zimoun's message of "Tue, 21 Jan 2020 14:32:00 +0100")
Hi!
zimoun <zimon.toutoune@gmail.com> skribis:
> Currently, the proposed Guix to install is v1.0.1. This very version
> has some "bugs" [1] fixed since then [2]. But it is not convenient
> when using with Docker [3].
>
> Why not update the minor version to v1.1?
It’s definitely time for this, and I agree with the “1.1” number, FWIW.
:-)
However, I would really want to have good automated tests of the
installer before this happens:
https://lists.gnu.org/archive/html/guix-devel/2020-01/msg00225.html
Likewise, if someone could come up with a test for the binary tarball
installation on top of, say, Debian, that’d be great! (Probably not a
blocker, but still helpful in giving more confidence about the release.)
Surely this could be done in QEMU with a dummy HTTP(S) proxy.
I’m sure there are other issues in the bug tracker that’d be worth
addressing.
Help welcome!
Ludo’.
prev parent reply other threads:[~2020-01-23 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 13:32 Guix minor version update? zimoun
2020-01-21 15:37 ` Pierre Neidhardt
2020-01-21 17:43 ` Julien Lepiller
2020-01-22 1:35 ` Bengt Richter
2020-01-23 16:28 ` Ludovic Courtès
2020-01-24 16:31 ` Jonathan Frederickson
2020-01-24 17:08 ` zimoun
2020-01-23 15:42 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftg6qivs.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.