Bug#768976: unblock: fail2ban/0.9.1-1

[Yaroslav Halchenko <debian@onerussian.com>]

Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package fail2ban

We have 0.8.13 in jessie ATM and I have released 0.9.1 and uploaded 0.9.1-1
just few days too short of a freeze - 10days (why didn't I change urgency? ;))

[2014-10-28] Accepted fail2ban 0.9.1-1 (source all) into unstable (Yaroslav Halchenko)

0.9.1 is the 2nd release in the 0.9.0 line and I had 0.9.0 in experimental for
a while.  So far it shows great promise to be very stable and much more
versatile than 0.8.x -- we introduced multiline matching, eliminated divergance
between Debian's and upstream jail.conf definitions, extended testing a lot
(92% code coverage).  After the release I haven't seen major bug reports (there
is one minor typo to be fixed) and I have high confidence that this release
would be a much better fit to maintain in Debian jessie (instead of now very
stable but aging fast 0.8.). 

debdiff would be infeasible (we also made it a proper fail2ban python module
instead of a bunch of internal submodules), but let me know if I need to
provide more lines of argumentation to feature unblock

unblock fail2ban/0.9.1-1

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.17-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash