unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Soo <jsoo1@asu.edu>
To: Joshua Branson <jbranso@dismail.de>
Cc: guix-devel@gnu.org
Subject: Re: “Which important packages fail to build?”
Date: Sat, 26 Jan 2019 09:38:44 -0500	[thread overview]
Message-ID: <58784805-FAA9-4134-B535-A7A96B6E3AAB@asu.edu> (raw)
In-Reply-To: <87fttfr069.fsf@dismail.de>

Hi,

I think icecat is ok. I’m probably wrong about this but what I understand is that icecat is being rebuilt after the rust bootstrap got merged. Upgrading icecat now requires building several versions of the rust compiler. I hope a substitute becomes available soon since it really does take a long time. I have a pretty nice set of hardware and it took nearly a day. I can’t imagine on an older machine.

- John

> On Jan 26, 2019, at 8:57 AM, Joshua Branson <jbranso@dismail.de> wrote:
> 
> Ludovic Courtès <ludo@gnu.org> writes:
> 
>> Hello Guix!
>> 
>> I’ve just added a new ‘--coverage’ option to ‘guix weather’.  The goal
>> is to answer the question: “which important packages fail to build?”, or
>> at least, “which important packages have no substitutes?”.  I believe
>> this is what we want to know in particular to determine whether a branch
>> can be merged.  Demonstration:
>> 
>> $ ./pre-inst-env  guix weather --substitute-urls=https://ci.guix.info -c 10
>> computing 8,983 package derivations for x86_64-linux...
>> looking for 9,343 store items on https://ci.guix.info...
>> updating substitutes from 'https://ci.guix.info'... 100.0%
>> https://ci.guix.info
>>  64.7% substitutes available (6,048 out of 9,343)
>>  18,642.5 MiB of nars (compressed)
>>  54,068.6 MiB on disk (uncompressed)
>>  0.018 seconds per request (164.6 seconds in total)
>>  56.8 requests per second
>>  'https://ci.guix.info/api/queue?nr=1000' returned 504 ("Gateway Time-out")
>> updating substitutes from 'https://ci.guix.info'... 100.0%
>> 2502 packages are missing from 'https://ci.guix.info' for 'x86_64-linux', among which:
>>    58  kcoreaddons@5.49.0      /gnu/store/8v69bzi29rla9q952ajgpsvsb7k955l6-kcoreaddons-5.49.0
>>    47  kcoreaddons@5.49.0      /gnu/store/8v69bzi29rla9q952ajgpsvsb7k955l6-kcoreaddons-5.49.0
>>    46  qgpgme@1.11.1   /gnu/store/rgvjzck002diandc1nhkw0dy1p9zqaw2-qgpgme-1.11.1
>>    37  perl-http-cookiejar@0.008       /gnu/store/2npd0vs3ipyqms06kbgh7ialp9n0fr6m-perl-http-cookiejar-0.008
>>    30  qgpgme@1.11.1   /gnu/store/rgvjzck002diandc1nhkw0dy1p9zqaw2-qgpgme-1.11.1
>>    26  ocaml4.02-ppx-deriving@4.1      /gnu/store/siv42br9h06i1zhmmj6s2qian45zacgm-ocaml4.02-ppx-deriving-4.1
>>    18  ruby-ansi@1.5.0 /gnu/store/p5adbp7bhvjzpjxr8brnfm52imqc4f07-ruby-ansi-1.5.0
>>    16  cl-rt@1990.12.19        /gnu/store/vs9ddw7avffmnzxcknvyazay29vihy28-cl-rt-1990.12.19
>>    16  ecl-rt@1990.12.19       /gnu/store/765znwnf4bxdaz82akx60pkx2ac59fyn-ecl-rt-1990.12.19
>>    13  ecl-trivial-gray-streams@0.0.0-1.0483ade        /gnu/store/lyj6w0p9v3kfkzmar1pd46qlg36zp7dd-ecl-trivial-gray-streams-0.0.0-1.0483ade
>>    11  ruby-brass@1.2.1        /gnu/store/jxf63lbwv2rg95pf5zmznjzv8s367xqc-ruby-brass-1.2.1
>>    11  ruby-rspec-expectations@2.14.5  /gnu/store/6dacx02mn2skwbiajfwnx1q0fk5iw05y-ruby-rspec-expectations-2.14.5
>>    11  ruby-rspec-mocks@2.14.6 /gnu/store/9lirirccwslkghpps1al23m7pdi5yw1b-ruby-rspec-mocks-2.14.6
>>    11  ruby-rspec-core@2.14.8  /gnu/store/xrpaql4jldvvd08im37x8k42crsxpip0-ruby-rspec-core-2.14.8
>>    11  ecl-slynk-boot0@1.0.0-beta-2.cbf84c3    /gnu/store/l23p319knfzygsc38zxf7l5g892bqy1z-ecl-slynk-boot0-1.0.0-beta-2.cbf84c3
>>    11  python2-oslotest@3.4.0  /gnu/store/7f87w09iinxv06dld394x7w47chcy3ip-python2-oslotest-3.4.0
>>    10  pt-scotch@6.0.5a        /gnu/store/gw4mzjlwlf010ijhyznhr5sjmpxizl9v-pt-scotch-6.0.5a
> 
> As an aside, should Icecat be on this list?  I keep having to use "guix package
> --do-not-upgrade=icecat -u", because Icecat takes forever to build, and
> I'm not certain that I have enough memory to build it.
> 
> However,
> 
> #BEGIN_SRC sh
> icecat --version
> #END_SRC
> 
> #+:RESULTS:
> GNU IceCat 60.3.0
> 
> 
> BUT why does guix package -u try to rebuild Icecat?
> 
> #BEGIN_SRC sh
> guix package -u
> guix package: warning: package 'jmacs' no longer exists
> substitute: updating substitutes from 'https://ci.guix.info'... 100.0%
> building /gnu/store/r583x6jd6qlb7im42c0awmj6jvi1g13c-icecat-60.3.0-gnu1.drv...
> #END_SRC
> 
> 
> P.S. jmacs is my attempt to have a "custom" Emacs.  It's basically Emacs
> with additional modules installed.
> 
> Thanks,
> 
> Joshua
> 
> --
> Joshua Branson
> Sent from Emacs and Gnus
> 

  reply	other threads:[~2019-01-26 14:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-25 13:22 “Which important packages fail to build?” Ludovic Courtès
2019-01-25 14:22 ` Ricardo Wurmus
2019-01-25 23:04   ` Ludovic Courtès
2019-01-25 19:47 ` Christopher Baines
2019-01-26 13:57 ` Joshua Branson
2019-01-26 14:38   ` John Soo [this message]
2019-01-26 15:32   ` Ricardo Wurmus
2019-01-28 10:33     ` Ludovic Courtès

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=58784805-FAA9-4134-B535-A7A96B6E3AAB@asu.edu \
    --to=jsoo1@asu.edu \
    --cc=guix-devel@gnu.org \
    --cc=jbranso@dismail.de \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).