Compiles fine and works fine. It has been more than 30 days testing. Bug 168071 is less than 30 days ago. However that patch does not change anything about the program. So please stabilize. Portage 2.1.2-r9 (default-linux/amd64/2007.0/no-multilib, gcc-4.1.1, glibc-2.5-r0, 2.6.20-gentoo x86_64) ================================================================= System uname: 2.6.20-gentoo x86_64 AMD Turion(tm) 64 Mobile Technology MT-28 Gentoo Base System release 1.12.9 Timestamp of tree: Fri, 02 Mar 2007 17:50:01 +0000 distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] dev-lang/python: 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=athlon64 -msse3 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c" CXXFLAGS="-march=athlon64 -msse3 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig collision-protect distcc distlocks metadata-transfer multilib-strict sandbox sfperms strict test" GENTOO_MIRRORS="http://gentoo.nedlinux.nl" LINGUAS="en nl" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage-overlay" SYNC="rsync://rsync.nedlinux.nl/gentoo-portage" USE="X alsa amd64 apache2 bitmap-fonts bzip2 cli cracklib crypt cups cvs dvd dvdr exif fam flac gdbm gif gstreamer iconv imagemagick ipod isdnlog jpeg jpeg2k kde libg++ md5sum midi mmx mp3 mplayer ncurses nls nomotif nptl nptlonly ogg opengl oss pcre pdf perl png ppds pppd python qt readline reflection samba session spl sse sse2 ssl tcpd test tetex truetype-fonts type1-fonts unicode vorbis xine xml xml2 xorg zlib" ALSA_CARDS="intel8x0" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="keyboard mouse synaptics" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en nl" USERLAND="GNU" VIDEO_CARDS="sis" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Don't cc the arches unless you are the maintainer.
I wish to add some "elog" lines in the ebuild first (like in Postfix, i.e. "you're upgrading from an incompatible version, fix your config files blablabla), because the migration to 0.7 is a big change. netmon, your opinion?
(In reply to comment #1) > Don't cc the arches unless you are the maintainer. > Sorry you are right. Won't happen again. However i would like it stabilized please. :) But Raphael Marichez is right. The config files are incompatible.
i've been talking with upstream who says that the stable branch (0.8) will be out soon. http://www.fail2ban.org/wiki/index.php/FAQ_english#What_does_the_version_number_of_Fail2ban_mean.3F The structure of the version number is major.minor.revision. Currently the major number is 0. The policy for minor is: * odd numbers (0.5, 0.7, etc) are development versions. * even numbers (0.6, 0.8, etc) are stable versions. According to http://www.fail2ban.org/wiki/index.php/ChangeLog , 0.7.6 is a beta version and 0.7.7 is the release candidate. I'll certainly put 0.7.7 in portage for our testing.
i've emailed upstream for an estimated date of 0.8.x release.
Hi Roeland, Cyril (upstream) told me that the 0.8 stable branch release is postponned to next month (may). Indeed there were a few bugreports and a second release-candidate has been released (0.7.9). I'm going to put that r-c into the tree. Are you OK to wait for 0.8.0 or do you really want to see one of the 0.7.x stabilized?
(In reply to comment #6) Thanks for thinking about me Raphael :) I can wait for version 0.8
Hi all, 0.8.0 is out. There is only minor changes since 0.7.9. http://sourceforge.net/forum/forum.php?forum_id=692565 If you stabilize 0.8.0, please do not forget that configuration is *not* compatible. I have written a small howto. You could maybe add a link in "elogs" about it. http://www.fail2ban.org/wiki/index.php/HOWTO_Upgrade_from_0.6_to_0.8 Thanks
