From owner-svn-ports-head@FreeBSD.ORG Fri May 2 16:01:24 2014 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B8A564C8; Fri, 2 May 2014 16:01:24 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA256 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 53A7B1AAE; Fri, 2 May 2014 16:01:23 +0000 (UTC) Received: from [192.168.1.100] ([46.115.148.210]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0LtVLE-1WpzIN3NZc-010vfv; Fri, 02 May 2014 18:01:16 +0200 Message-ID: <5363C176.6050100@gmx.at> Date: Fri, 02 May 2014 18:01:58 +0200 From: Christoph Theis User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Andrey Chernov , Sunpoet Po-Chuan Hsieh , 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 References: <201405021317.s42DHQ5P053302@svn.freebsd.org> <5363A968.7010707@freebsd.org> In-Reply-To: <5363A968.7010707@freebsd.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:e95/zHtQtQiQQh+ucESyKzJo4bO2Jkawm9cdJ6/HAEvv0IOSwgD yN6fj9r8bycExNBc04ROFVztrDPyaxxLdk7/8djieVuMOKSTWCmbbMf6jiAF8Bx6lH+BoMg 0ubRNigCkihIjo8LN7dj8vyuGyo/KpwWJTlT39sUOjsW2khd1yMyKUdHGD1a0zDGrH5CI4m RRpLZ3cObimCV/IbJCmMg== X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2014 16:01:24 -0000 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?