From: Greg Hogan <code@greghogan.com>
To: 60020@debbugs.gnu.org
Cc: Greg Hogan <code@greghogan.com>
Subject: [bug#60020] [PATCH 0/8] Update openjdk.
Date: Mon, 12 Dec 2022 21:18:38 +0000 [thread overview]
Message-ID: <cover.1670879700.git.code@greghogan.com> (raw)
These look to be the latest updates to openjdk11+.
The openjdk build process creates thousands of defunct bash processes,
necessitating the increase in maximum number of tasks.
Greg Hogan (8):
Increase "TasksMax" in 'guix-daemon.service'.
gnu: openjdk11: Update to 11.0.17.
gnu: openjdk13: Update to 13.0.13.
gnu: openjdk15: Update to 15.0.9.
gnu: openjdk16: Update to 16.0.2.
gnu: openjdk17: Update to 17.0.5.
gnu: openjdk18: Update to 18.0.2.
gnu: openjdk: Update to 19.
etc/guix-daemon.service.in | 2 +-
gnu/packages/java.scm | 44 +++++++++++++++++++++++++++-----------
2 files changed, 32 insertions(+), 14 deletions(-)
--
2.38.1
next reply other threads:[~2022-12-12 21:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 21:18 Greg Hogan [this message]
2022-12-12 21:19 ` [bug#60020] [PATCH 1/8] Increase "TasksMax" in 'guix-daemon.service' Greg Hogan
2022-12-12 21:19 ` [bug#60020] [PATCH 2/8] gnu: openjdk11: Update to 11.0.17 Greg Hogan
2022-12-12 21:19 ` [bug#60020] [PATCH 3/8] gnu: openjdk13: Update to 13.0.13 Greg Hogan
2022-12-12 21:19 ` [bug#60020] [PATCH 4/8] gnu: openjdk15: Update to 15.0.9 Greg Hogan
2022-12-12 21:19 ` [bug#60020] [PATCH 5/8] gnu: openjdk16: Update to 16.0.2 Greg Hogan
2022-12-12 21:19 ` [bug#60020] [PATCH 6/8] gnu: openjdk17: Update to 17.0.5 Greg Hogan
2022-12-12 21:19 ` [bug#60020] [PATCH 7/8] gnu: openjdk18: Update to 18.0.2 Greg Hogan
2022-12-12 21:19 ` [bug#60020] [PATCH 8/8] gnu: openjdk: Update to 19 Greg Hogan
2023-01-16 17:59 ` [bug#60020] [PATCH 0/8] Update openjdk Maxim Cournoyer
2023-01-17 16:04 ` Greg Hogan
2023-01-17 19:38 ` Maxim Cournoyer
2023-01-18 9:40 ` Efraim Flashner
2023-01-18 15:03 ` bug#60020: " Greg Hogan
2023-01-18 15:45 ` [bug#60020] " Maxim Cournoyer
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=cover.1670879700.git.code@greghogan.com \
--to=code@greghogan.com \
--cc=60020@debbugs.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).