From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: new GuixSD version?
Date: Wed, 20 Jul 2016 15:34:46 +0200 [thread overview]
Message-ID: <87a8hcbfgp.fsf@gnu.org> (raw)
In-Reply-To: <20160720055939.GA12944@jasmine> (Leo Famulari's message of "Wed, 20 Jul 2016 01:59:39 -0400")
Leo Famulari <leo@famulari.name> skribis:
> On Wed, Jul 20, 2016 at 12:45:49AM -0400, Ethan Stefan Day wrote:
>> -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)
>
> We should at least be able to re-add the source code to Hydra, and
> hopefully the binaries. Since the source code is content-addressed, it
> can be fetched from many places, such as the local /gnu/store, an URL,
> the substitutes server, and also content-addressed mirrors [0] (but not
> in 0.10.0).
I think the main problem is that some of the 0.10.0 binaries have
vanished from {mirror.,}hydra.gnu.org. Thus, people installing GuixSD
for the first time today have a very bad experience.
We can rebuild the ‘release-0-10’ branch on Hydra, but of course we’re
limited by the available resources.
At any rate, Ethan: I think we’ll make a 0.10.1 release once we’ve merge
‘core-updates’, which could be a week or two from now.
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-07-20 13:34 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
2016-07-20 5:59 ` Leo Famulari
2016-07-20 13:34 ` Ludovic Courtès [this message]
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=87a8hcbfgp.fsf@gnu.org \
--to=ludo@gnu.org \
--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).