all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: guix-devel@gnu.org
Subject: Re: 1.1.0rc1 available for test!
Date: Fri, 10 Apr 2020 13:24:27 +0200	[thread overview]
Message-ID: <87k12n37o4.fsf@gmail.com> (raw)
In-Reply-To: <87369c1ixm.fsf@gnu.org>

Hello,

Running the graphical installer from the installation image hosted
through IPFS, I can report the following experience:

The guidance, keyboard configuration & partitioning works well.  In fact
all goes charmingly until the stage where the sysconf is shown.  That
looks correct too.

Hitting continue at that point switches to a terminal wher I briefly see
cow-store being started.

Then the screen flashes back to the beginning of the installer.  Running
through the process again results in the disk drive not being available
for partitioning.

I cannot see any error messages in the brief time I see the terminal and
am not sure how to get an error log.

Happy to run some more commands to get additional information.

Best wishes,

Alex

Ludovic Courtès <ludo@gnu.org> writes:

> Hello Guix!
>
> I’ve run “make release” from the new ‘version-1.1.0’ branch and uploaded
> the result:
>
>   https://web.fdn.fr/~lcourtes/software/guix/1.1.0rc1
>
> Alternately (and preferably), you can get it over IPFS:
>
>   guix install ipfs
>   ipfs daemon &
>   ipfs ls QmXpSUnppJgf23LpaKJzRWJbQxwEfybJy9VxF79iTLSXqa
>   ipfs get …
>
> All the files are signed with my key, also used to sign this message.
>
> Please test things as much as you can, be it the binary installation
> tarball on a “foreign” distro or the ISO image.  Once you’ve downloaded,
> just follow the same instructions as before (if you want to use
> ‘guix-install.sh’, you’ll have to adjust it to use the right tarball):
>
>   https://guix.gnu.org/download/
>
> If you encounter an issue, please report it to bug-guix@gnu.org,
> explaining what you did and what you observed.
>
> Notice that there’s no i686-linux installation image and no VM image,
> because of <https://issues.guix.gnu.org/issue/40527> but i can provide
> those later.
>
> If everything goes well, we can publish the release on Monday, 13th,
> with few or no changes beyond translation updates on the ‘version-1.1.0’
> branch.
>
> Thanks in advance!  :-)
>
> Ludo’.

  parent reply	other threads:[~2020-04-10 11:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09 20:51 1.1.0rc1 available for test! Ludovic Courtès
2020-04-09 21:33 ` Danny Milosavljevic
2020-04-10  1:56 ` pelzflorian (Florian Pelz)
2020-04-10 10:38   ` Ludovic Courtès
2020-04-10 12:06   ` Mathieu Othacehe
2020-04-10 14:35   ` pelzflorian (Florian Pelz)
2020-04-10 14:47     ` pelzflorian (Florian Pelz)
2020-04-13 18:12       ` pelzflorian (Florian Pelz)
2020-04-10  3:20 ` Vagrant Cascadian
2020-04-10 10:29   ` Ludovic Courtès
2020-04-10 11:24 ` Alex Sassmannshausen [this message]
2020-04-10 12:01   ` Mathieu Othacehe
2020-04-10 12:19     ` Alex Sassmannshausen
2020-04-10 12:07   ` Alex Sassmannshausen
2020-04-10 12:17     ` Mathieu Othacehe
2020-04-10 13:11       ` Alex Sassmannshausen
2020-04-10 13:53       ` Mathieu Othacehe
2020-04-10 14:19         ` Ludovic Courtès
2020-04-10 16:02           ` Alex Sassmannshausen
2020-04-10 15:42 ` Alex Sassmannshausen
2020-04-10 22:38   ` Ludovic Courtès
2020-04-11  9:11     ` alex sassmannshausen
2020-04-11 13:16       ` Amin Bandali
2020-04-11 13:48         ` Pierre Neidhardt
2020-04-10 15:45 ` Alex Sassmannshausen
2020-04-11 10:51 ` Vincent Legoll
2020-04-11 22:26   ` Ludovic Courtès
2020-04-12  6:43     ` Vincent Legoll
2020-04-13 10:50       ` Ludovic Courtès
2020-04-13 11:46         ` Vincent Legoll
2020-04-13 12:36         ` Vincent Legoll
2020-04-13 16:14         ` Vincent Legoll
2020-04-13 20:24           ` Ludovic Courtès

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=87k12n37o4.fsf@gmail.com \
    --to=alex.sassmannshausen@gmail.com \
    --cc=guix-devel@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.
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.