From: Leo Famulari <leo@famulari.name>
To: Ethan Stefan Day <esday@ethan-stefan.net>
Cc: help-guix@gnu.org
Subject: Re: new GuixSD version?
Date: Wed, 20 Jul 2016 01:59:39 -0400 [thread overview]
Message-ID: <20160720055939.GA12944@jasmine> (raw)
In-Reply-To: <60114a63-ccdf-2677-cb97-5fa8a90cd406@ethan-stefan.net>
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).
In the worst case, users can find new source URLs and use `guix
download` to add the source code of missing binaries whose source URLs
have changed to the store.
We should think about how to make the release tags more resilient.
> 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.
Yes, please report anything that's missing.
[0]
http://git.savannah.gnu.org/cgit/guix.git/commit/?id=cd436bf05a8344acf4462f3602e7d360821a902a
next prev parent reply other threads:[~2016-07-20 6:01 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 [this message]
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=20160720055939.GA12944@jasmine \
--to=leo@famulari.name \
--cc=esday@ethan-stefan.net \
--cc=help-guix@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.
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).