From owner-freebsd-stable@freebsd.org Wed Aug 30 13:01:45 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 40765E0172B; Wed, 30 Aug 2017 13:01:45 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.shmhost.net (unknown [IPv6:2a01:4f8:a0:51d6::108:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 059CD6C18B; Wed, 30 Aug 2017 13:01:45 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from francos-mbp.seppmail (business-24-134-14-193.pool2.vodafone-ip.de [24.134.14.193]) by host64.shmhost.net (Postfix) with ESMTPSA id BC5D28117B; Wed, 30 Aug 2017 15:01:31 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: pkg issue after FreeBSD 11 upgrade From: Franco Fichtner In-Reply-To: Date: Wed, 30 Aug 2017 15:01:30 +0200 Cc: Baptiste Daroussin , freebsd-stable@freebsd.org, Matthew Seaman , "freebsd-ports@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <4c16c960-3b4a-75ab-41ed-51c8109b940a@FreeBSD.org> <20170830124855.ph5cca5pwjd2pphf@ivaldir.net> To: Cassiano Peixoto X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at host64.shmhost.net X-Virus-Status: Clean X-Spam-Flag: NO X-Spam-Score: -1.0 X-Spam-Status: No score=-1.0 tagged_above=10.0 required=10.0 tests=[ALL_TRUSTED] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2017 13:01:45 -0000 Hi Cassiano, > On 30. Aug 2017, at 2:55 PM, Cassiano Peixoto = wrote: >=20 > Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 = only. It was a later 10.x change as far as I know. > Is there some flag to disable it? Or some hack that I could do? No. At OPNsense we use a patch to revert the behaviour. = https://github.com/opnsense/ports/blob/master/ports-mgmt/pkg/files/patch-l= ibpkg_scripts.c Cheers, Franco=