From: gevisz <gevisz@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: sci-libs/spqr-1.2.3-r1 failed to emerge
Date: Thu, 9 Apr 2020 14:46:11 +0300 [thread overview]
Message-ID: <CA+t6X7fuFnDbLCf3VvAScCgBRbWr=2o3VV33DzVR+NKxQf46tA@mail.gmail.com> (raw)
In-Reply-To: <r6mj2a$2jis$1@ciao.gmane.io>
чт, 9 апр. 2020 г. в 10:32, Nuno Silva <nunojsilva@ist.utl.pt>:
>
> On 2020-04-09, gevisz wrote:
>
> > ср, 8 апр. 2020 г. в 19:31, gevisz <gevisz@gmail.com>:
> >>
> >> ср, 8 апр. 2020 г. в 18:13, Michael Orlitzky <mjo@gentoo.org>:
> >> >
> >> > The other thing you should be aware of is that dev-lang/julia is, from a
> >> > software engineering point of view, an absolute trainwreck (upstream,
> >> > not the Gentoo maintainer's fault). Your experience so far is going to
> >> > be typical, I fear.
> >>
> >> After I added all these files to the
> >> /etc/portage/package.accept_keywords/julia file,
> >> julia finally emerged. Thank you. However, I am affraid what will be
> >> when I try to update my Gentoo system in a month or so.
> >
> > A small addition: I've just noticed that I've managed to emerge only
> > julia-1.3.0;
> > julia-1.4.0-r1 still fails to be emerged (at a compile phase).
>
> What errors?
>
> There is bug 716434[1] where julia fails because it tries to download
> more tarballs (yes, during compilation). An ebuild change was made to
> address this, so it might be worth syncing the tree and trying to emerge
> again.
Thank you. I will try.
> [1] https://bugs.gentoo.org/show_bug.cgi?id=716434
next prev parent reply other threads:[~2020-04-09 11:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 10:37 [gentoo-user] sci-libs/spqr-1.2.3-r1 failed to emerge gevisz
2020-04-08 10:29 ` [gentoo-user] " Nuno Silva
2020-04-08 14:19 ` gevisz
2020-04-08 14:45 ` gevisz
2020-04-08 13:00 ` Neil Bothwick
2020-04-08 15:01 ` gevisz
2020-04-08 15:12 ` Michael Orlitzky
2020-04-08 16:31 ` gevisz
2020-04-09 6:49 ` gevisz
2020-04-09 7:32 ` Nuno Silva
2020-04-09 11:46 ` gevisz [this message]
2020-04-09 13:19 ` gevisz
2020-04-09 4:28 ` [gentoo-user] " David Haller
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='CA+t6X7fuFnDbLCf3VvAScCgBRbWr=2o3VV33DzVR+NKxQf46tA@mail.gmail.com' \
--to=gevisz@gmail.com \
--cc=gentoo-user@lists.gentoo.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