Hi Cyril, On Wed, Apr 01, 2020 at 05:01:22AM +0200, Cyril Brulebois wrote: > Hi, > > Salvatore Bonaccorso <car...@debian.org> (2020-03-06): > > [disclaimer not part of maintainers of fail2ban but was looking as > > issues in fail2ban and stumpbled over this bug] > > Noted. > > > there was an upload of fail2ban to unstable based on the 0.11 branch > > now, and Jakob mentioned that there support for actually purging > > entries from database were in that branch. > > > > Is the issue fixed with with any of the 0.11.1-1~exp1 upload? > > (0.11.1-1 was uploaded to unstable). > > I'm a little reluctant to trying a package from unstable into > production, with that amount of changes: > > 214 files changed, 9409 insertions(+), 3757 deletions(-) > > The bug closure doesn't even seem certain (“hopefully”)…
Understandable, would not do as as well to install unstable packages into production systems. Was just hoping you have a way to trigger/reproduce and confirm. Syvestre did close the bug in https://bugs.debian.org/933749#27 so if someone affected can confirm this would be great. Otherwise whoever encounters it after 0.11.1-1 can re-open the bug. Regards, Salvatore
