unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 51443-close@debbugs.gnu.org
Subject: bug#51443: [patch] openjdk11: update to latest version
Date: Wed, 03 Nov 2021 08:29:22 +0100	[thread overview]
Message-ID: <874k8td7ar.fsf@web.de> (raw)
In-Reply-To: <20211103021713.4d924e15@tachikoma.lepiller.eu>

[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]


Julien Lepiller <julien@lepiller.eu> writes:

> Le Wed, 27 Oct 2021 20:49:02 +0200,
> "Dr. Arne Babenhauserheide" <arne_bab@web.de> a écrit :
>
>> "Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
>> 
>> > The attached patch updates openjdk11 to the latest version. The
>> > update includes some important bugfixes for compile errors of
>> > classfiles.  
>> 
>> > +    (version "11.0.12-ga")  
>> 
>> This is from https://wiki.openjdk.java.net/display/JDKUpdates/JDK11u

> Thanks for the pach!
>
> I actually just pushed an update to 11.0.13, since 11.0.12 has a bunch
> of CVEs now (I was prompted to do the update when seeing an advisory
> from debian). Sorry that your patch did not get in, but hopefully you
> can now enjoy an updated openjdk11 :)

No problem — thank you for updating! My goal was getting the new
version in, not getting the exact patch in :-)

(I’ve been running 11.0.12-ga from my local patched sources, so I wasn’t
blocked)

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

      reply	other threads:[~2021-11-03  7:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 17:23 bug#51443: [patch] openjdk11: update to latest version Dr. Arne Babenhauserheide
2021-10-27 18:49 ` Dr. Arne Babenhauserheide
2021-11-03  1:17   ` Julien Lepiller
2021-11-03  7:29     ` Dr. Arne Babenhauserheide [this message]

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=874k8td7ar.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=51443-close@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    /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).