From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: java: switch to icedtea-8 as default JDK Date: Sat, 6 Jan 2018 21:16:44 +0100 Message-ID: References: <877etlo2fq.fsf@elephly.net> <87y3lzgmy1.fsf@gmail.com> <877etiz7uu.fsf@elephly.net> <87incg48ed.fsf@elephly.net> <87tvvyrdkn.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="f403043cb0947cb48b0562213e1e" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43142) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eXute-0006O3-1B for guix-devel@gnu.org; Sat, 06 Jan 2018 15:16:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eXutb-0006O2-Gu for guix-devel@gnu.org; Sat, 06 Jan 2018 15:16:50 -0500 Received: from mail-io0-x235.google.com ([2607:f8b0:4001:c06::235]:34913) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eXutb-0006KU-Ba for guix-devel@gnu.org; Sat, 06 Jan 2018 15:16:47 -0500 Received: by mail-io0-x235.google.com with SMTP id 14so9176385iou.2 for ; Sat, 06 Jan 2018 12:16:46 -0800 (PST) In-Reply-To: <87tvvyrdkn.fsf@gmail.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Chris Marusich Cc: guix-devel --f403043cb0947cb48b0562213e1e Content-Type: text/plain; charset="UTF-8" Actually we still have a couple of build failures, some test failures, and the commit messages are not conformant to the policy. Currently making the few remainig failures work should be the primary task. I will check the details. I already have an integration branch where I reorder commits and make commit messages conform. It would also be nice, if you could review the patches already sent to guix-patches. They are tagged [PATCH core-updates]. I guess we are waiting for the next core-updates cycle, until then these will not be pushed. These are the backwards compatible changes collected so far. Soon I will add the fix for the antlr3 bootstrap toolchain. Current issues: https://github.com/Boskovits/guix/issues/61 I'm will contact upstream to check if this issue is serious. Will cc to you. https://github.com/Boskovits/guix/issues/58 I will have a look at this once more. I've already solved two similar issues, I guess I can cope with this. https://github.com/Boskovits/guix/issues/57 I'm not sure about this one. I can try to check upstream if this is a problem on their site, but it seems not. It seems that some zeromq calls fail. Can this be related to our build container? https://github.com/Boskovits/guix/issues/56 I haven't looked into this one yet. https://github.com/Boskovits/guix/issues/55 I intend to remove this package if axoloti-patcher works with the current version. I did not do this yet, because the java-simple-xml issue also blocks axoloti-patcher, so I could not check yet if the current version is ok. The remaining five issues are the packages from the covering of icedtea7 that do not build. The rest does build. I don't know if we have any more issues between the marked problems and these five packages. > -- > Chris > --f403043cb0947cb48b0562213e1e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Actually we still have a couple of build failures, some te= st failures, and the
commit messages are not conformant to the policy. = Currently making the few remainig
failures work should be the pri= mary task. I will check the details.
I already have an integratio= n branch where I reorder commits and make commit messages conform.
It would also be nice, if you could review the patches already sent to gu= ix-patches.
They are tagged [PATCH core-updates]. I guess we are = waiting for the next core-updates cycle, until then
these will no= t be pushed.

These are the backwards compatible ch= anges collected so far.
Soon I will add the fix for the antlr3 bo= otstrap toolchain.

Current issues:

<= /div>
I'm will contact u= pstream to check if this issue is serious.
Will cc to you.
<= div>
I will have a= look at this once more.
I've already solved two similar issu= es, I guess I can cope with this.

I'm not sure about this one.
I can= try to check upstream if this is a problem on their site, but it seems not= .
It seems that some zeromq calls fail.
Can this be rel= ated to our build container?

I haven't looked into this one yet.
I intend to remove t= his package if
axoloti-patcher works with the current version.
I did not do this yet, because the
java-simple-xml issue = also blocks axoloti-patcher,
so I could not check yet if the curr= ent version is ok.

The remaining five issues are t= he packages from
the covering of icedtea7 that do not build.
The rest does build.

I don't know if we = have any more issues between the
marked problems and these five p= ackages.


--
Chris

--f403043cb0947cb48b0562213e1e--