From owner-freebsd-ports@freebsd.org Thu Feb 9 15:30:24 2017 Return-Path: Delivered-To: freebsd-ports@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 BC2F2CD7778 for ; Thu, 9 Feb 2017 15:30:24 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A79D3BC2 for ; Thu, 9 Feb 2017 15:30:24 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: by mailman.ysv.freebsd.org (Postfix) id A4132CD7777; Thu, 9 Feb 2017 15:30:24 +0000 (UTC) Delivered-To: ports@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 A3B8BCD7776 for ; Thu, 9 Feb 2017 15:30:24 +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 6D043BC1; Thu, 9 Feb 2017 15:30:24 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from francos-mbp.homeoffice.local (dslb-092-078-013-237.092.078.pools.vodafone-ip.de [92.78.13.237]) by host64.shmhost.net (Postfix) with ESMTPSA id 18303849CF; Thu, 9 Feb 2017 16:30:21 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?! From: Franco Fichtner In-Reply-To: <35a953e3-918b-fc32-d990-51f7da16c884@FreeBSD.org> Date: Thu, 9 Feb 2017 16:30:20 +0100 Cc: scratch65535@att.net, freebsd-ports Content-Transfer-Encoding: 7bit Message-Id: References: <1c6cccac-b151-d13c-c763-b336c4680118@freebsd.org> <35a953e3-918b-fc32-d990-51f7da16c884@FreeBSD.org> To: Steve Wills X-Mailer: Apple Mail (2.3259) X-Virus-Scanned: clamav-milter 0.99.2 at host64.shmhost.net X-Virus-Status: Clean X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2017 15:30:24 -0000 Hi Steve, > On 9 Feb 2017, at 4:09 PM, Steve Wills wrote: > > Ports and packages are maintained on the assumption that the user is > using a supported version of the OS. We didn't decide when to end > support for 10.1 or 10.2. How long after the end of life for 10.1 would > you have ports maintain support? The issue is quite simple and cause of multiple issues: FreeBSD package management makes an ABI promise in the form of "FreeBSD:10:amd64", but not even pkg code itself adheres to this, and thus we have had subtle and yet fatal breakage in 10.2 and 10.3. And since pkg acts according to the imposed paradigm of a unified ABI, this will continue to be a source of problems for users who cannot know what's going on, lest even know how to fix it. They simply run: # pkg upgrade And then their systems are unusable *and* not fixable with pkg. What are they supposed to do? They come here. They want to make everyone aware that this is a serious issue that shouldn't repeat in FreeBSD 11. It's not to late to do that by pinning the pkg ABI to 11.0 by forcing the proper feature macros. Cheers, Franco