unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: GNU Guix 1.3.0rc1 available for testing!
Date: Sat, 1 May 2021 17:25:45 -0400	[thread overview]
Message-ID: <YI3HWXLF0N4eY45K@jasmine.lan> (raw)
In-Reply-To: <877dkjovl6.fsf@gmail.com>

On Sat, May 01, 2021 at 01:45:57AM -0400, Maxim Cournoyer wrote:
>     https://alpha.gnu.org/gnu/guix/guix-binary-1.3.0rc1.x86_64-linux.tar.xz

I tested the binary tarball on x86_64.

I used `guix package --export-manifest > manifest` before beginning the
test, so that I could easily recreate my profile afterwards.

> All these files have an associated ‘.sig’, an OpenPGP signature that you
> can verify as explained at
> <https://guix.gnu.org/manual/en/html_node/Binary-Installation.html>.

These instructions explain how to get Ludo's key, but that wasn't used
here.

In doc/guix.texi, the variables OPENPGP-SIGNING-KEY-ID and
OPENPGP-SIGNING-KEY-URL are defined.

Maybe we should update the manual to mention "1.3.0rc1" and the correct
key.

The "normal" manual would still mention 1.2.0, but the devel manual
would work for 1.3.0rc1. I think that it's fine to mention the release
candidate in the "devel" manual.

https://guix.gnu.org/manual/en/
https://guix.gnu.org/manual/devel/en/

> 
>   1. Testing the binary tarball on the distro of your choice.  You can
>      download <https://guix.gnu.org/install.sh>.  Uncomment the
>      ‘GNU_URL’ variable assignment that refers to alpha.gnu.org and it
>      should pick up 1.3.0rc1 automatically.

The install.sh script also recommends installing Ludo's key, but of
course fails to verify the signature with it. After installing Ludo's
key, the installer does suggest the correct key — Maxim's.

Aside from that, the install.sh script worked fine on current Debian,
and I was able to conveniently restore my Guix profile with `guix
package -m ./manifest`.

Then I did `guix pull && guix upgrade`. All good!

I forgot to remove the existing Guix build users and the guixbuild group
before my test. It would be great if somebody can remember to check that
they are created successfully by the script.


  parent reply	other threads:[~2021-05-01 21:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-01  5:45 GNU Guix 1.3.0rc1 available for testing! Maxim Cournoyer
2021-05-01  7:48 ` Vagrant Cascadian
2021-05-02  2:53   ` Maxim Cournoyer
2021-05-01 21:25 ` Leo Famulari [this message]
2021-05-02  2:52   ` Maxim Cournoyer
2021-05-02  4:27     ` Leo Famulari
2021-05-04  4:02       ` Maxim Cournoyer
2021-05-02  4:05   ` Leo Famulari
2021-05-02  4:28     ` Leo Famulari
2021-05-02 18:45     ` Maxim Cournoyer
2021-05-02 22:14       ` Leo Famulari
2021-05-03 19:38 ` Tissevert
2021-05-04  0:34   ` Leo Famulari
2021-05-05  8:16     ` Tissevert
2021-05-05 17:01     ` Vagrant Cascadian
2021-05-06  1:18       ` Leo Famulari
2021-05-05  1:49 ` Chris Marusich

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=YI3HWXLF0N4eY45K@jasmine.lan \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@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 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).