Date: Tue, 2 Aug 2011 12:56:40 GMT From: Henrik Larsson <freebsd@spambox.dk> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/159384: ports/py27-fail2ban, custom jail.conf file overwritten after upgrade Message-ID: <201108021256.p72CueGn022746@red.freebsd.org> Resent-Message-ID: <201108021300.p72D0MaE091085@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 159384 >Category: ports >Synopsis: ports/py27-fail2ban, custom jail.conf file overwritten after upgrade >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue Aug 02 13:00:22 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Henrik Larsson >Release: >Organization: >Environment: >Description: After an upgrade of the py27-fail2ban port from py27-fail2ban-0.8.4_1 to py27-fail2ban-0.8.4_2, the edited /usr/local/etc/fail2ban/jail.conf file is overwritten with the default one. I used the following command to upgrade: "portmaster py27-fail2ban" Is this the expected behavior? If yes, how can I keep my edited jail.conf during upgrades of this port? Best regards Henrik Larsson >How-To-Repeat: - Install old version of py27-fail2ban port - Edit /usr/local/etc/fail2ban/jail.conf - Upgrade py27-fail2ban port - The jail.conf file is now back to default >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201108021256.p72CueGn022746>