From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add Icedtea 3.0.0pre09
Date: Fri, 25 Mar 2016 11:27:05 +0100 [thread overview]
Message-ID: <87a8lmsvie.fsf@gnu.org> (raw)
In-Reply-To: <877fh04wk0.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 17 Mar 2016 22:35:43 +0100")
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
>
>> the latest icedtea-ified JDK has not yet been released, but this doesn’t
>> mean we can’t package it.
>>
>> Attached is a patch to add “icedtea-8” (because it provides the JDK for
>> Java version 1.8). It uses the upstream tarball for version 3.0.0pre09,
>> which I had to mirror on my own server because the Guile HTTP client
>> doesn’t like an invalid header in the response from
>> http://icedtea.classpath.org.
>
> On IRC there was the idea to provide “url-fetch/wget” which would be
> less strict compared to the default Guile HTTP client.
We could do that, but I would prefer fixing and/or monkey-patching the
date header check in Guile.
In this case, if the problem is date header validation, it seems that we
could monkey-patch the ‘parse-rfc-822-date’ procedure of (web http) to
do the right thing.
Would you like to give it a try?
>> The version is declared as “2.99.99-pre09” so that version “3.0.0” (when
>> it is finally released) will be considered an update.
>
> Does it make sense to push this patch to master? Or should we wait for
> an official release? Java 1.8 is already pretty old and it seems like
> the pre-release is enough to build OpenJDK 8.
I’d rather wait for an official release, but maybe there’s a good reason
to use the pre-release?
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-03-25 10:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 15:40 [PATCH] gnu: Add Icedtea 3.0.0pre09 Ricardo Wurmus
2016-03-11 9:58 ` Roel Janssen
2016-03-11 13:32 ` Ricardo Wurmus
2016-03-11 15:24 ` Roel Janssen
2016-03-17 21:35 ` Ricardo Wurmus
2016-03-25 10:27 ` Ludovic Courtès [this message]
2016-03-25 12:26 ` Ricardo Wurmus
2016-03-25 12:49 ` Ludovic Courtès
2016-04-19 12:48 ` Ricardo Wurmus
2016-04-21 20:39 ` Roel Janssen
2016-03-26 9:11 ` Ricardo Wurmus
2016-03-26 14:36 ` 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=87a8lmsvie.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).