Github messages for voidlinux
 help / color / mirror / Atom feed
From: 2asoft <>
Subject: [PR PATCH] jetbrains-jdk-bin: update to 11.0.10b1379.1.
Date: Thu, 18 Mar 2021 07:02:49 +0100	[thread overview]
Message-ID: <> (raw)

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

There is a new pull request by 2asoft against master on the void-packages repository 2asoft/jb_update_jdk

jetbrains-jdk-bin: update to 11.0.10b1379.1.
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

A patch file from is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-2asoft/jb_update_jdk-29555.patch --]
[-- Type: text/x-diff, Size: 1288 bytes --]

From df00edc074c2f9ff88cbf17d55ce2375d1b5e378 Mon Sep 17 00:00:00 2001
From: Anton Afanasyev <>
Date: Wed, 17 Mar 2021 22:46:57 -0700
Subject: [PATCH] jetbrains-jdk-bin: update to 11.0.10b1379.1.

 srcpkgs/jetbrains-jdk-bin/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/jetbrains-jdk-bin/template b/srcpkgs/jetbrains-jdk-bin/template
index 1521c48bfaa9..aa5fd1078ac3 100644
--- a/srcpkgs/jetbrains-jdk-bin/template
+++ b/srcpkgs/jetbrains-jdk-bin/template
@@ -1,6 +1,6 @@
 # Template file for 'jetbrains-jdk-bin'
@@ -12,7 +12,7 @@ homepage=""
 fetch_cmd="wget --quiet"
 # This JDK appears to link to libs that do not exist, but functions well even in their absence.
 # Best guess is that they are optional. ¯\_(ツ)_/¯

             reply	other threads:[~2021-03-18  6:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18  6:02 2asoft [this message]
2021-03-18 14:06 ` [PR PATCH] [Merged]: " sgn

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:

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

  git send-email \ \ \ \

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