all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: icedtea-1, icedtea-2 security updates
Date: Thu, 28 Jan 2016 08:27:14 +0100	[thread overview]
Message-ID: <87mvrqjh9p.fsf@elephly.net> (raw)
In-Reply-To: <20160128042529.GA5869@jasmine>


Leo Famulari <leo@famulari.name> writes:

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

Thanks for trying!  I won’t be able to attend to this before Tuesday, so
it’s nice that somebody else is taking care of this.

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

Not only icedtea (i.e. the patches to the OpenJDK sources to make it
buildable with free software) has to be updated, but also the “drops”.
Drops are upstream OpenJDK source tarballs.

So for icedtea-6 this means the "openjdk6-src" input must be changed to

    https://java.net/downloads/openjdk6/openjdk-6-src-b38-20_jan_2016.tar.gz;
    
for icedtea-7 all of the added native-inputs must be changed, i.e:
"openjdk-src", "corba-drop", "jaxp-drop", "jaxws-drop", "jdk-drop",
"langtools-drop", "hotspot-drop".

The icedtea-7 package has a function to build origins from names and
hashes, so you will just need to update the version and the individual
drop hashes.  You can get all the icedtea-7 drops here:

    http://icedtea.wildebeest.org/download/drops/icedtea7/2.6.4/

Hope this helps!

~~ Ricardo

  reply	other threads:[~2016-01-28  7:27 UTC|newest]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mvrqjh9p.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.