From: swedebugia <swedebugia@riseup.net>
To: George Clemmer <myglc2@gmail.com>, Mark H Weaver <mhw@netris.org>
Cc: help-guix@gnu.org
Subject: Re: *** TRYING TO INSTALL GUIXSD v0.15.0 FOR DAYS ***
Date: Tue, 6 Nov 2018 16:27:03 +0100 [thread overview]
Message-ID: <cd4c824d-fddb-6078-b25c-61f86815616d@riseup.net> (raw)
In-Reply-To: <cuczhut3bh0.fsf@gmail.com>
Hi
On 2018-11-01 01:09, George Clemmer wrote:
snip
> And, with the current state of the guix infrastructure, even a 'guix
> pull' on a fresh vm-image triggers guile bootstrap. And a guile
> bootstrap, on the best of days, displays these symptoms: howling CPUs
> and hardly any disk activity.
>
> So, relative to what one expects when installing a distro this feels
> hung. Not the most confidence inspiring experience to subject a guix
> noob to ;-)
>
I react a little on the wording of you last phrase.
We did not subject anyone to anything.
Trying out beta software like guix (especially when our servers are
down) and pulling the latest guix commit is in my view (with my earlier
guix-experience) asking for trouble.
Pulling a commit like the one that points to 0.15 see
http://git.savannah.gnu.org/cgit/guix.git/tag/?h=v0.15.0 is far better -
I did that 2 days ago with no trouble. No building locally of the few
packages I needed on a bare-bone install, berlin had 30-40% of the
substitutes available.
Thus what we could do to improve the situation is to instruct users to
NOT pull the latest guix unless they know what they are doing or are
willing to deal with anything that comes up...
We do a rolling release with NO testing branch currently. So everybody
who pulls the latest and greatest is a tester willingly or not.
--
Cheers
Swedebugia
next prev parent reply other threads:[~2018-11-06 15:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 15:42 *** TRYING TO INSTALL GUIXSD v0.15.0 FOR DAYS *** Brian Woodcox
2018-10-31 17:41 ` Leo Famulari
2018-10-31 18:23 ` Brian Woodcox
2018-10-31 18:35 ` Mark H Weaver
2018-10-31 18:47 ` Brian Woodcox
2018-11-01 7:35 ` Mark H Weaver
2018-10-31 20:50 ` Brian Woodcox
2018-10-31 21:54 ` George Clemmer
2018-10-31 22:30 ` Brian Woodcox
2018-10-31 23:44 ` George Clemmer
2018-11-01 2:33 ` Mark H Weaver
2018-11-01 3:35 ` George Clemmer
2018-10-31 22:47 ` Mark H Weaver
2018-10-31 23:57 ` George Clemmer
2018-11-01 0:09 ` George Clemmer
2018-11-06 15:27 ` swedebugia [this message]
2018-11-06 18:24 ` George Clemmer
2018-11-07 11:40 ` swedebugia
2018-11-07 13:01 ` George Clemmer
2018-11-07 15:16 ` Christopher Lemmer Webber
2018-11-01 1:35 ` Mark H Weaver
2018-11-01 2:58 ` Brian Woodcox
2018-11-06 5:14 ` Mark H Weaver
2018-11-06 17:08 ` Brian Woodcox
2018-11-06 23:22 ` Brian Woodcox
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=cd4c824d-fddb-6078-b25c-61f86815616d@riseup.net \
--to=swedebugia@riseup.net \
--cc=help-guix@gnu.org \
--cc=mhw@netris.org \
--cc=myglc2@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 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.