From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: openjdk11: update to 11.0.12+7, cleanup, split jre & jmods into subpkgs
Date: Thu, 28 Apr 2022 00:34:12 +0200 [thread overview]
Message-ID: <20220427223412.fzPkmNboBpQHllUq5DxwhBdIxHgo9DyDnQMe-d5QhlI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36520@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1754 bytes --]
There's a merged pull request on the void-packages repository
openjdk11: update to 11.0.12+7, cleanup, split jre & jmods into subpkgs
https://github.com/void-linux/void-packages/pull/36520
Description:
- openjdk11: clean up template
- New package: openjdk11-jre-11.0.12+5
- New package: openjdk11-jmods-11.0.12+5
- openjdk11: disable on armv[56]*
- openjdk11: update to 11.0.12+7, enable debug.
fixes #25183
fixes #29457
closes #36221
This should bring openjdk11 more in-line with other openjdk package templates
See [here](https://forums.raspberrypi.com/viewtopic.php?t=232680), [here](https://forums.raspberrypi.com/viewtopic.php?t=323376), and [here](https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255662) for evidence of the arm incompatibility.
cc: @knusbaum for maintainer review
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- x86_64-musl
- i686
- aarch64(-musl)
- armv7l(-musl)
[ci skip]
prev parent reply other threads:[~2022-04-27 22:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 16:29 [PR PATCH] openjdk11: cleanup, split jre into subpackage classabbyamp
2022-04-04 16:31 ` [PR PATCH] [Updated] " classabbyamp
2022-04-04 16:36 ` classabbyamp
2022-04-04 17:47 ` classabbyamp
2022-04-04 19:58 ` classabbyamp
2022-04-04 21:04 ` classabbyamp
2022-04-19 15:30 ` classabbyamp
2022-04-20 2:26 ` classabbyamp
2022-04-20 23:54 ` classabbyamp
2022-04-21 0:15 ` [PR PATCH] [Updated] openjdk11: cleanup, split jre, jmods " classabbyamp
2022-04-21 1:25 ` [PR PATCH] [Updated] openjdk11: update to 11.0.12+7, cleanup, split jre & jmods into subpkgs classabbyamp
2022-04-21 1:28 ` classabbyamp
2022-04-21 3:31 ` classabbyamp
2022-04-25 15:05 ` classabbyamp
2022-04-25 15:10 ` classabbyamp
2022-04-25 17:16 ` classabbyamp
2022-04-25 18:46 ` classabbyamp
2022-04-27 15:14 ` classabbyamp
2022-04-27 22:34 ` leahneukirchen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220427223412.fzPkmNboBpQHllUq5DxwhBdIxHgo9DyDnQMe-d5QhlI@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).