unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: swedebugia@riseup.net
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: help-guix@gnu.org,
	Help-Guix <help-guix-bounces+swedebugia=riseup.net@gnu.org>
Subject: Re: very few substitutes available?
Date: Sat, 05 Jan 2019 11:39:03 -0800	[thread overview]
Message-ID: <cf8094b52aa8d3778daa8cbee6d0646e@riseup.net> (raw)
In-Reply-To: <20190105.182420.2018021984926348743.post@thomasdanckaert.be>

On 2019-01-05 18:24, Thomas Danckaert wrote:
> Hi guix,
> 
> I've been attempting to update my profile for a while now (actually
> the latest generation is already from july... :-) ).  I find that I
> always have to build a huge number of packages, such as the entire
> rust bootstrap & icecat...  I've been stuck in a loop where I run
> “guix pull”, wait a few days, see that I still have to build icecat,
> and try “guix pull” again, ...
> 
> How long does it typically take before substitutes are available after
> pulling from master?  Or is there a way to see (from ci.guix.info?)
> which revision I should pull in order to have a maximum of substitutes
> available?

Are you on 32 or 64 bit?
Paste "uname -a" 

I had the same experience on 32-bit a month ago. 64-bit is way way
better supported by the build-farms currently for bug/technical reasons.

If you are on 32-bit you have some choices:
- change to a 64-bit machine
- wait for the builds to be done or someone to fix it
- help us find and restart the failed builds (ask Mark on guix-devel)
- build them yourself and share using ipfs and the wip-branch published
a few days ago. and invite other 32-bit users to do the same.
- sack the packages causing the rebuilds and find alternatives. E.g.
rust is drawn in by icecat. Switch to epiphany, etc.

Gnome perhaps draws in an awful lot of builds. Try xfce or stumpwm which
is way way lighter.

Given that you are the first one to notice/write about this in the
latest few months beside me I guess there are very few 32-bit users in
guixland right now so the best option might be to upgrade to 64-bit and
follow the herd.

-- 
Cheers 
Swedebugia

  reply	other threads:[~2019-01-05 19:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-05 17:24 very few substitutes available? Thomas Danckaert
2019-01-05 19:39 ` swedebugia [this message]
2019-01-06 13:14   ` Thomas Danckaert
2019-01-06 16:39     ` Ricardo Wurmus
2019-01-11 21:26       ` Thomas Danckaert
2019-01-11 22:07         ` Leo Famulari
2019-01-12  7:11         ` Ricardo Wurmus

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=cf8094b52aa8d3778daa8cbee6d0646e@riseup.net \
    --to=swedebugia@riseup.net \
    --cc=help-guix-bounces+swedebugia=riseup.net@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=post@thomasdanckaert.be \
    /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).