From owner-freebsd-stable@freebsd.org Wed Aug 30 13:05:05 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 99AC8E018F9; Wed, 30 Aug 2017 13:05:05 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 75D5B6C477; Wed, 30 Aug 2017 13:05:05 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id D122D1FF24; Wed, 30 Aug 2017 13:05:04 +0000 (UTC) Date: Wed, 30 Aug 2017 15:05:04 +0200 From: Baptiste Daroussin To: Franco Fichtner Cc: Cassiano Peixoto , freebsd-stable@freebsd.org, Matthew Seaman , "freebsd-ports@freebsd.org" Subject: Re: pkg issue after FreeBSD 11 upgrade Message-ID: <20170830130504.kgbwkztaomnqq3hy@ivaldir.net> References: <4c16c960-3b4a-75ab-41ed-51c8109b940a@FreeBSD.org> <20170830124855.ph5cca5pwjd2pphf@ivaldir.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="u7bfalyehqj2uupg" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170714 (1.8.3) 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:05:05 -0000 --u7bfalyehqj2uupg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 30, 2017 at 03:01:30PM +0200, Franco Fichtner wrote: > Hi Cassiano, >=20 > > 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. >=20 > It was a later 10.x change as far as I know. >=20 > > Is there some flag to disable it? Or some hack that I could do? >=20 > No. At OPNsense we use a patch to revert the behaviour. >=20 > https://github.com/opnsense/ports/blob/master/ports-mgmt/pkg/files/patch-= libpkg_scripts.c Why and what is your use case, there is a reason why this code has been add= ed, and I would like to hear more about use cases so we can try to address them. Best regards, Bapt --u7bfalyehqj2uupg Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlmmuAAACgkQY4mL3PG3 PlqxuQ//flVXRlQHww9kjQ9i7iVEVLKcodNCqX6mHQTLmp/fuYBmDILgw4My5IPK xJzcR8FPfeiNSuPRL3jAXKwrWoSc2w+HgnGO8AsCPULHNuylsVIoAqe1L/dibjfn LmxekNfiZgb/mrcKswjZRfLxyhLNkkhqoKt4bIeMBgtHvRa8DKFIImuJnwZLVYiz MpeUyJSLGYrdcO+0xyZwXVVCElz2FZV9OlbC+WYlJBbIvStIybEmix5ZavuWMGgj lcEOt2iNuPiGB7R1O3Og+X3hGsSRf4BxnRYQW4aiHc0HUjYO5MlHtdWYgL7Xt3JZ Ztanh6YOFGavYPHbG4//fIuvPz3Lx7olrrCreWP6IjbwNlcKDxnctWo1SnjUzS/A jbj70jpN8MgUa/tZFq2rrdLf3kAF/4mR52xdTR06NcvZmWmfAld+p7NmBnprmkax FgYZ2g6HdyCY132dOBejJ5Iq6yjmg5TpVaVjjdThezLMxMs1FtjuL83V/c3RP8lt 5CrTvzWEyMPSxz7xNzGShRNSurv97gPc0M4kbUqgMhQNL8UQgGv+b0tgOK07j1WV kJADTLFjrNJcwzc8EjxhHHh5GI1VCiL9QMpE/ZnEdj7Qf1HoI4oNKOy4WNtQYrQW rk4O9X/UBRbia9L4aZMn1gBH+rDXZ1V/j9ldo7LrpCfg5FH2tFs= =aLYO -----END PGP SIGNATURE----- --u7bfalyehqj2uupg--