adjusted README: removed part about missing chain because the issue is

resolved by now
Also postinst announces about necessity to upgrade the config file

debian/README.Debian

@@ -32,15 +32,6 @@ just a single group (?P<host>...)
 
 [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=330827
 
-Broken chain:
-
-Currently no checks if an iptables queue generated at the beginning
-(fail2ban-http and fail2ban-ssh) exists. So if your firewall resets the iptable
-rules -- it is your responsibility to restart fail2ban.  Also you can
-augment fwban and fwunban rules and include as first lines full
-definitions of fwstart. That is nasty solution and probably it will get
-resolved in the future.
-
 Mailing:
 
 As it was reported (bug #329722) you might need to provide a full
@@ -52,4 +43,4 @@ work nicely now
 See TODO.Debian for more details, as well as the Debian Bug Tracking
 system.
 
- -- Yaroslav O. Halchenko <debian@onerussian.com>, Sat Oct  1 02:47:46 2005
+ -- Yaroslav O. Halchenko <debian@onerussian.com>, Wed Oct 12 13:14:48 2005

debian/changelog

@@ -1,4 +1,4 @@
-fail2ban (0.5.4-5.8) unstable; urgency=low
+fail2ban (0.5.4-5.9) unstable; urgency=low
 
   * Added a notification regarding the importance of 0.5.4-5 change of
     failregex in the config file.

debian/postinst

@@ -26,18 +26,28 @@ case "$1" in
 
        # Note regarding changed configuration file
 		if [ ! -z $preversion ] \
-			&& dpkg --compare-versions $preversion lt 0.5.4-5;
+			&& dpkg --compare-versions $preversion lt 0.5.4-6;
 			then
-			cat <<EOF 
+			cat <<EOF
 WARNING!
- Configuration file /etc/fail2ban.conf, failregex configuration parameter
- specificly, were changed in 0.5.4-5 to close reported security breach.
 
+ Configuration file /etc/fail2ban.conf, failregex configuration
+ parameter specificly, were changed in 0.5.4-5 to close reported
+ security breach, and in 0.5.4-6 to close few other bugs.
+
+updating from <0.5.4-5
  Unless configuration file (or corresponding failregex'es) gets updated,
  security breach is not closed and corresponding warning will be reported
  by the fail2ban (in the log files).
 
- Please review the configuration file and make appropriate changes. 
+updating from <0.5.4-6
+ Bugs #329163, #331695 dealing with changed iptables rules
+ outside of fail2ban were fixed in 0.5.4-6, and require upgrade of the
+ configuration file (fwcheck option was introduced) to take full
+ advantage of the problem solution (otherwise some problems might
+ persist)
+
+ Please review the configuration file and make appropriate changes.
 ENJOY!
 
 EOF