unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: icedtea-1, icedtea-2 security updates
Date: Wed, 27 Jan 2016 23:25:29 -0500	[thread overview]
Message-ID: <20160128042529.GA5869@jasmine> (raw)

There are security updates for icedtea-1 [0] and icedtea-2 [1]. The
updated versions are 1.3.10 and 2.6.4, respectively.

I spent some time trying to build these new versions but I am having
trouble.

The upstream tarballs contain their own patches on the bundled OpenJDK
source code. For both icedtea-1 and icedtea-2, some of these patches
fail to apply.

I looked into the failing patches to see if it could be fixed by
adjusting, for example, the whitespace the parameters of `patch`, but
the strings to be matched don't exist in the relevant files.

I _think_ this is an upstream bug. However, the icedtea-* package
definitions are complex and I'd like it if someone else could take a
look at this issue before I file an upstream bug report.

Some details follow about the problem in icedtea-2.

The failing patch file is:
icedtea-2.6.4/patches/boot/ecj-multicatch.patch

... and it fails while trying to patch:
jdk/src/share/classes/sun/security/ssl/RSAClientKeyExchange.java

... on the first "diff" line of the patch:
 -        } catch (InvalidAlgorithmParameterException |

The string "InvalidAlgorithmParameterException" does not exist in that
file.

Thanks for your attention.

[0]
http://blog.fuseyism.com/index.php/2016/01/25/security-icedtea-1-13-10-for-openjdk-6-released/
[1]
http://blog.fuseyism.com/index.php/2016/01/21/security-icedtea-2-6-4-for-openjdk-7-released/

             reply	other threads:[~2016-01-28  4:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28  4:25 Leo Famulari [this message]
2016-01-28  7:27 ` icedtea-1, icedtea-2 security updates Ricardo Wurmus
2016-01-28 13:52   ` Leo Famulari

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=20160128042529.GA5869@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.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.
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).