Date: Fri, 02 May 2014 18:01:58 +0200 From: Christoph Theis <theis@gmx.at> To: Andrey Chernov <ache@freebsd.org>, Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r352813 - in head/security/py-fail2ban: . files Message-ID: <5363C176.6050100@gmx.at> In-Reply-To: <5363A968.7010707@freebsd.org> References: <201405021317.s42DHQ5P053302@svn.freebsd.org> <5363A968.7010707@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 02.05.2014 16:19, schrieb Andrey Chernov:
> On 02.05.2014 17:17, Sunpoet Po-Chuan Hsieh wrote:
>> - Update to 0.9.0
>
> ${FAIL2BAN_DBDIR} is not created on install for the reason unknown.
In my patch I had a rule
post-install:
@${MKDIR} ${FAIL2BAN_DBDIR}
In the commit it became a
post-install:
@${MKDIR} ${STAGEDIR}${FAIL2BAN_DBDIR}
@Hsieh: As a workaround create the /var/db/fail2ban manually
@Andrey: My intention was to create that directory during installation.
I think it is wrong to create it in $STAGEDIR instead during
post-install. But what would be the correct way to create a /var/db
directory used at runtime only and nothing is copied there during
installation?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5363C176.6050100>