From: Ethan Stefan Day <esday@ethan-stefan.net>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: new GuixSD version?
Date: Wed, 20 Jul 2016 00:45:49 -0400 [thread overview]
Message-ID: <60114a63-ccdf-2677-cb97-5fa8a90cd406@ethan-stefan.net> (raw)
In-Reply-To: <20160720035513.GA21435@jasmine>
[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]
On 07/19/2016 11:55 PM, Leo Famulari wrote:
> On Tue, Jul 19, 2016 at 05:36:50PM -0400, Ethan Stefan Day wrote:
>> Will be a new version of GuixSD installation image once the dust settles
>> from the Hydra outage and the Sourceforge URL issue? I ask because as I
>> understand it, it will be impossible to install from that image without
>> running 'guix pull' inside the installer, and I think I recall someone
>> on guix-devel saying to not do that.
>
> Can you clarify why you think it would be impossible to install from the
> 0.10.0 GuixSD image? Hopefully that's not the case...
>
The installer requires additional software to be downloaded. I have not
checked to see if this is actually the case, but it seems likely that
there is an intersection between the set of packages required to be
downloaded at install time, the set of packages whose binaries were lost
in the Hydra failure, the set of packages affected by the Sourceforge
URL issue, and the set of packages whose hashes have changed since
GuixSD 0.10.0 was released. If that is the case, then there exists a
package P such that:
-The installer requires P to proceed.
-Hydra does not have the binary for P (it is silently ignoring bad URLs).
-The '--fallback' option for 'guix system init' will not work because of
the bad URLs. (although I think the intent was for users to not have to
use that anyway)
If my concern is based on accurate understanding, I would be willing to
test it. I was about to reinstall GuixSD on metal for unrelated reasons.
-Ethan Day
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-20 4:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 21:36 new GuixSD version? Ethan Stefan Day
2016-07-20 3:55 ` Leo Famulari
2016-07-20 4:45 ` Ethan Stefan Day [this message]
2016-07-20 5:59 ` Leo Famulari
2016-07-20 13:34 ` Ludovic Courtès
2016-07-20 14:13 ` Vincent Legoll
2016-07-21 11:35 ` Ludovic Courtès
2016-07-21 11:44 ` Vincent Legoll
2016-07-21 12:00 ` Ludovic Courtès
2016-07-21 19:23 ` Ethan Stefan Day
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=60114a63-ccdf-2677-cb97-5fa8a90cd406@ethan-stefan.net \
--to=esday@ethan-stefan.net \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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).