From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-analyzer/hydra/
Date: Wed, 13 Apr 2022 04:55:09 +0000 (UTC) [thread overview]
Message-ID: <1649825701.00d854ad87a75f20d241173633ba730a27736ec4.sam@gentoo> (raw)
commit: 00d854ad87a75f20d241173633ba730a27736ec4
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Apr 13 04:54:25 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Apr 13 04:55:01 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=00d854ad
net-analyzer/hydra: GTK 3 port is broken
It doesn't seem to actually build against 3, configure wasn't regenerated
properly.
Bug: https://bugs.gentoo.org/838031
Signed-off-by: Sam James <sam <AT> gentoo.org>
net-analyzer/hydra/{hydra-9.3.ebuild => hydra-9.3-r1.ebuild} | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/net-analyzer/hydra/hydra-9.3.ebuild b/net-analyzer/hydra/hydra-9.3-r1.ebuild
similarity index 93%
rename from net-analyzer/hydra/hydra-9.3.ebuild
rename to net-analyzer/hydra/hydra-9.3-r1.ebuild
index aa7d807e29b8..d149fdce2dde 100644
--- a/net-analyzer/hydra/hydra-9.3.ebuild
+++ b/net-analyzer/hydra/hydra-9.3-r1.ebuild
@@ -3,7 +3,7 @@
EAPI=8
-inherit toolchain-funcs
+inherit autotools toolchain-funcs
DESCRIPTION="Parallelized network login hacker"
HOMEPAGE="https://github.com/vanhauser-thc/thc-hydra"
@@ -21,7 +21,7 @@ RDEPEND="
dev-libs/atk
dev-libs/glib:2
x11-libs/gdk-pixbuf:2
- x11-libs/gtk+:3
+ x11-libs/gtk+:2
)
firebird? ( dev-db/firebird )
gcrypt? ( dev-libs/libgcrypt )
@@ -58,6 +58,12 @@ src_prepare() {
-e '/^OPTS/{s|=|+=|;s| -O3||}' \
-e '/ -o /s:$(OPTS):& $(LDFLAGS):g' \
Makefile.am || die
+
+ # Needed to get GTK+ 3 change in configure.in (.in got updated, but
+ # configure not regen'd.)
+ #cd hydra-gtk || die
+ #sed -i -e 's:AC_INIT(configure.in):AC_INIT(configure.ac):' configure.in || die
+ #eautoreconf
}
src_configure() {
next reply other threads:[~2022-04-13 4:55 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 4:55 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-15 20:25 [gentoo-commits] repo/gentoo:master commit in: net-analyzer/hydra/ Mike Gilbert
2024-03-17 16:35 Mike Gilbert
2024-03-17 16:35 Mike Gilbert
2023-11-04 16:13 Arthur Zamarin
2023-11-04 12:25 Sam James
2022-12-16 7:39 Sam James
2022-04-13 4:55 Sam James
2022-01-15 21:51 Sam James
2021-05-01 18:19 Agostino Sarubbo
2021-04-30 18:46 Mikle Kolyada
2021-03-26 7:45 Agostino Sarubbo
2021-03-19 2:08 Sam James
2021-03-19 2:00 Sam James
2021-03-15 22:09 Sam James
2021-03-15 21:01 Sam James
2021-03-15 21:01 Sam James
2021-03-15 21:01 Sam James
2021-03-15 21:01 Sam James
2021-01-02 15:45 Andreas K. Hüttel
2020-09-14 19:31 Michał Górny
2020-08-03 20:59 Jeroen Roovers
2020-07-29 9:37 Jeroen Roovers
2020-02-02 22:28 Matt Turner
2020-01-27 14:52 Jeroen Roovers
2019-10-29 16:38 Jeroen Roovers
2019-10-12 10:21 Michał Górny
2019-10-07 4:52 Jeroen Roovers
2019-08-13 6:22 Jeroen Roovers
2019-08-13 6:22 Jeroen Roovers
2019-05-17 16:28 Jeroen Roovers
2019-04-01 8:41 Jeroen Roovers
2019-02-14 20:09 Brian Evans
2017-07-27 13:26 Jeroen Roovers
2017-07-27 13:26 Jeroen Roovers
2017-05-06 9:03 Jeroen Roovers
2017-05-06 8:57 Jeroen Roovers
2017-05-06 8:57 Jeroen Roovers
2016-07-13 17:36 Anthony G. Basile
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=1649825701.00d854ad87a75f20d241173633ba730a27736ec4.sam@gentoo \
--to=sam@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