fail2ban doesn't include the proper deps. It leaves out iptables. aaron@zoom ~ % emerge --info Portage 2.1_pre6 (default-linux/amd64/2006.0, gcc-3.4.4, glibc-2.3.5-r2, 2.6.15-gentoo-r7 x86_64) ================================================================= System uname: 2.6.15-gentoo-r7 x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.6.14 dev-lang/python: 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=athlon64 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon64 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig buildpkg ccache cvs digest distlocks fixpackages metadata-transfer multilib-strict sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.ussg.iu.edu/pub/linux/gentoo" LANG="en_US.UTF-8" LC_ALL="en_US.UTF-8" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 acl alsa avi bitmap-fonts crypt dri eds emboss encode fastcgi foomaticdb fortran ftp gif gpm gstreamer gtk2 imlib innodb jpeg libwww lzw lzw-tiff maildir mp3 mpeg mysql ncurses nptl nptlonly opengl pam pdflib perl png python quicktime readline ruby sdl spell ssl tcpd tetex tidy tiff truetype-fonts type1-fonts usb xml xv zlib elibc_glibc kernel_linux userland_GNU" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, LDFLAGS, LINGUAS
Ok. It should only go in RDEPEND, correct?
Yes sir. That would be it.
Thanks, in cvs.
Could this be changed to a USEflag thing? According to the README, fail2ban also supports shorewall and even hosts.deny methods, so this should be a user's choice, not a builtin dependency. I've been using fail2ban successfully with hosts.deny for several months.
(In reply to comment #4) > Could this be changed to a USEflag thing? > > According to the README, fail2ban also supports shorewall and even hosts.deny > methods, so this should be a user's choice, not a builtin dependency. I've been > using fail2ban successfully with hosts.deny for several months. Looks interesting to me.
Created attachment 104166 [details] fail2ban-0.6.2.ebuild After discussing the issue with marienz, I think maybe USEflags are overkill. The ebuild should not depend on anything (besides >python-2.4), and should install the extra configs as examples in /usr/share/doc. That's what this ebuild does. I also have updated copies of the other ebuilds. Let me know if you want me to upload them.
Fixed in CVS
*** Bug 316493 has been marked as a duplicate of this bug. ***