From: "Ronny Gutbrod" <gentoo@tastytea.de>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: dev-cpp/drogon/
Date: Thu, 8 Sep 2022 01:46:42 +0000 (UTC) [thread overview]
Message-ID: <1662585821.b17bcfbab92af06106c34350cc70266495251d6c.tastytea@gentoo> (raw)
Message-ID: <20220908014642.ACwhvaYJvjBDGZRX66__V21bEM_ReLiRxPobNo_B3RM@z> (raw)
commit: b17bcfbab92af06106c34350cc70266495251d6c
Author: Ronny (tastytea) Gutbrod <gentoo <AT> tastytea <DOT> de>
AuthorDate: Wed Sep 7 18:53:39 2022 +0000
Commit: Ronny Gutbrod <gentoo <AT> tastytea <DOT> de>
CommitDate: Wed Sep 7 21:23:41 2022 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=b17bcfba
dev-cpp/drogon: fix trantor dependency
This prevents segfaults like in bug 868930, but the same tests still
fail in seemingly the same frequency.
Bug: https://bugs.gentoo.org/868930
Signed-off-by: Ronny (tastytea) Gutbrod <gentoo <AT> tastytea.de>
dev-cpp/drogon/{drogon-1.8.0.ebuild => drogon-1.8.0-r1.ebuild} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-cpp/drogon/drogon-1.8.0.ebuild b/dev-cpp/drogon/drogon-1.8.0-r1.ebuild
similarity index 98%
rename from dev-cpp/drogon/drogon-1.8.0.ebuild
rename to dev-cpp/drogon/drogon-1.8.0-r1.ebuild
index dfc208f1e..784892098 100644
--- a/dev-cpp/drogon/drogon-1.8.0.ebuild
+++ b/dev-cpp/drogon/drogon-1.8.0-r1.ebuild
@@ -21,7 +21,7 @@ IUSE="+brotli doc examples mariadb postgres redis sqlite +ssl test"
RESTRICT="!test? ( test )"
RDEPEND="
- >=dev-cpp/trantor-1.5.6:=
+ >=dev-cpp/trantor-1.5.6_pre20220801:=
dev-libs/jsoncpp:=
sys-libs/zlib
brotli? ( app-arch/brotli:= )
next reply other threads:[~2022-09-08 1:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 0:09 Ronny Gutbrod [this message]
2022-09-08 1:46 ` [gentoo-commits] repo/proj/guru:master commit in: dev-cpp/drogon/ Ronny Gutbrod
-- strict thread matches above, loose matches on Subject: below --
2024-07-21 15:16 [gentoo-commits] repo/proj/guru:dev " Ronny Gutbrod
2024-07-21 15:16 Ronny Gutbrod
2024-06-28 6:17 Ronny Gutbrod
2024-06-28 6:17 Ronny Gutbrod
2024-05-08 16:50 Ronny Gutbrod
2024-05-08 16:50 Ronny Gutbrod
2024-04-12 23:08 Ronny Gutbrod
2024-04-12 23:08 Ronny Gutbrod
2024-01-15 22:14 Ronny Gutbrod
2024-01-15 22:14 Ronny Gutbrod
2023-11-16 16:31 Ronny Gutbrod
2023-11-16 16:31 Ronny Gutbrod
2023-09-28 12:48 Ronny Gutbrod
2023-09-28 12:48 Ronny Gutbrod
2023-08-26 15:46 Ronny Gutbrod
2023-08-26 15:46 Ronny Gutbrod
2023-03-30 19:49 Ronny Gutbrod
2023-01-29 11:39 Ronny Gutbrod
2023-01-29 11:39 Ronny Gutbrod
2023-01-29 11:39 Ronny Gutbrod
2022-11-13 9:29 Ronny Gutbrod
2022-09-27 10:41 Ronny Gutbrod
2022-09-27 10:41 Ronny Gutbrod
2022-09-03 19:49 Ronny Gutbrod
2022-08-24 15:52 [gentoo-commits] repo/proj/guru:master " Ronny Gutbrod
2022-08-19 15:49 ` [gentoo-commits] repo/proj/guru:dev " Ronny Gutbrod
2022-08-19 15:49 Ronny Gutbrod
2022-02-26 8:06 Ronny Gutbrod
2022-02-26 8:06 Ronny Gutbrod
2021-12-12 15:28 Ronny Gutbrod
2021-12-12 15:28 Ronny Gutbrod
2021-12-01 11:52 Anna Vyalkova
2021-10-26 15:51 Ronny Gutbrod
2021-10-25 18:52 Ronny Gutbrod
2021-10-20 19:07 Ronny Gutbrod
2021-08-24 15:01 Ronny Gutbrod
2021-08-24 14:33 Ronny Gutbrod
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=1662585821.b17bcfbab92af06106c34350cc70266495251d6c.tastytea@gentoo \
--to=gentoo@tastytea.de \
--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