From: "Miroslav Šulc" <fordfrog@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-vpn/i2p/
Date: Thu, 23 May 2024 09:19:20 +0000 (UTC) [thread overview]
Message-ID: <1716455954.3184118ec41dc0396b37b920d05b150ad81538b1.fordfrog@gentoo> (raw)
commit: 3184118ec41dc0396b37b920d05b150ad81538b1
Author: Miroslav Šulc <fordfrog <AT> gentoo <DOT> org>
AuthorDate: Thu May 23 09:18:12 2024 +0000
Commit: Miroslav Šulc <fordfrog <AT> gentoo <DOT> org>
CommitDate: Thu May 23 09:19:14 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3184118e
net-vpn/i2p: fixed runtime java version on 2.5.2
Signed-off-by: Miroslav Šulc <fordfrog <AT> gentoo.org>
net-vpn/i2p/{i2p-2.5.2.ebuild => i2p-2.5.2-r1.ebuild} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net-vpn/i2p/i2p-2.5.2.ebuild b/net-vpn/i2p/i2p-2.5.2-r1.ebuild
similarity index 99%
rename from net-vpn/i2p/i2p-2.5.2.ebuild
rename to net-vpn/i2p/i2p-2.5.2-r1.ebuild
index 0230dbb8dd40..5cb884a1b827 100644
--- a/net-vpn/i2p/i2p-2.5.2.ebuild
+++ b/net-vpn/i2p/i2p-2.5.2-r1.ebuild
@@ -57,7 +57,7 @@ RDEPEND="
${CP_DEPEND}
acct-user/i2p
acct-group/i2p
- >=virtual/jre-1.8:*
+ >=virtual/jre-11:*
"
PATCHES=(
next reply other threads:[~2024-05-23 9:19 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 9:19 Miroslav Šulc [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-11 8:33 [gentoo-commits] repo/gentoo:master commit in: net-vpn/i2p/ Sam James
2024-11-28 0:09 Jakov Smolić
2024-10-17 15:32 Arthur Zamarin
2024-10-12 17:12 Arthur Zamarin
2024-09-28 13:30 Arthur Zamarin
2024-09-27 23:23 Jakov Smolić
2024-06-29 9:50 Miroslav Šulc
2024-06-29 6:22 Joonas Niilola
2024-05-24 11:02 Miroslav Šulc
2024-05-24 9:44 Florian Schmaus
2024-05-23 9:14 Florian Schmaus
2024-05-23 9:14 Florian Schmaus
2024-03-10 21:10 Miroslav Šulc
2024-03-10 21:10 Miroslav Šulc
2024-01-05 14:12 Sam James
2023-08-06 5:46 Miroslav Šulc
2023-08-01 11:22 Sam James
2023-07-18 17:21 Sam James
2023-07-18 17:21 Sam James
2023-07-18 16:32 Sam James
2023-07-18 16:32 Sam James
2023-07-15 13:15 Arthur Zamarin
2023-06-14 4:17 Sam James
2023-05-22 6:08 Miroslav Šulc
2023-05-20 11:08 Sam James
2022-08-05 6:57 Arthur Zamarin
2022-07-28 14:17 Sam James
2022-07-10 19:15 Arthur Zamarin
2022-07-10 6:17 Agostino Sarubbo
2022-05-24 14:42 Florian Schmaus
2022-05-24 14:42 Florian Schmaus
2022-03-12 12:01 Arthur Zamarin
2022-03-11 13:30 Joonas Niilola
2021-12-13 5:10 Sam James
2021-12-13 5:10 Sam James
2021-07-16 1:34 Sam James
2021-06-07 8:52 Miroslav Šulc
2020-12-11 7:58 Joonas Niilola
2020-12-11 7:58 Joonas Niilola
2020-09-13 0:44 Sam James
2020-03-21 16:13 Joonas Niilola
2020-03-21 16:13 Joonas Niilola
2020-01-29 6:14 Joonas Niilola
2020-01-16 5:49 Joonas Niilola
2020-01-06 15:40 Joonas Niilola
2020-01-06 15:40 Joonas Niilola
2019-11-13 6:03 Joonas Niilola
2019-06-05 8:54 Michał Górny
2019-06-05 8:54 Michał Górny
2019-04-22 10:17 Michał Górny
2018-10-14 10:33 Michał Górny
2018-10-14 10:33 Michał Górny
2018-09-07 8:24 Patrice Clement
2018-09-07 8:24 Patrice Clement
2018-08-26 17:40 Michał Górny
2018-04-03 15:28 Jonas Stein
2018-02-11 11:12 Michał Górny
2017-08-26 6:50 Patrick Lauer
2017-06-12 21:37 Patrice Clement
2017-05-23 14:28 Patrice Clement
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=1716455954.3184118ec41dc0396b37b920d05b150ad81538b1.fordfrog@gentoo \
--to=fordfrog@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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