From owner-freebsd-stable@FreeBSD.ORG Mon Dec 15 22:11:08 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8C7FFA5D for ; Mon, 15 Dec 2014 22:11:08 +0000 (UTC) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (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 43C4A156 for ; Mon, 15 Dec 2014 22:11:08 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 3F2E116A402; Mon, 15 Dec 2014 23:11:05 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTmm58agsyOg; Mon, 15 Dec 2014 23:10:55 +0100 (CET) Received: from [192.168.10.9] (vaio [192.168.10.9]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id C232816A407; Mon, 15 Dec 2014 23:10:55 +0100 (CET) Message-ID: <548F5C6F.7040309@digiware.nl> Date: Mon, 15 Dec 2014 23:10:55 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Brandon Allbery Subject: Re: I do not quite understand why a BIND upgrade needs to touch soo much. References: <548F4F62.4020308@digiware.nl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "ports@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2014 22:11:08 -0000 On 15-12-2014 22:26, Brandon Allbery wrote: > On Mon, Dec 15, 2014 at 4:20 PM, Brandon Allbery > wrote: >> >> On Mon, Dec 15, 2014 at 4:15 PM, Willem Jan Withagen >> wrote: >>> >>> So I'm building my packages with poudriere and using pkg (1.4.0) >>> to upgrade bind. With the sort of shocking result: >>> ====================== >>> Installed packages to be REMOVED: >>> gettext-0.18.3.1_1 >>> >> >> That first one is the key. Bind depends on gettext --- as does pretty much >> every other package in existence --- and gettext underwent a massive >> breaking change, which is kinda deranging everything else. The recent >> /usr/ports/UPDATING entry for gettext has the gory details. >> > > To explain a bit further: this time, your portupgrade would do a lot of > extra work as well. bind is not self-contained; it has dependencies, some > of which are shared by other packages. If you want your bind update to be > self-contained then you'll need to make your own port and package from it > containing its own gettext, so you can upgrade that one package without > breaking every other package that depends on gettext. Otherwise, you just > have to accept that a package other than bind, which bind and just about > everything else depends on, *also* changed; and you can't just upgrade bind > without upgrading gettext *and* either upgrading or removing the other > packages that depend on the old gettext. Yup, more than true in the ultimate case. Although 'portupgrade bind99' in this case did not require any other packages to be upgraded too. I've been hesitant in upgrading other packages with less security pressure, because of the huge list with extra's. And you are right, this change in gettext is going to bite at some point. (besides from building things with static linked libs.) Still leaves the point that 'pkg upgrade bind99' removes packages without reinstalling those. The only alternatives are: - pkg upgrade, and everything is upgraded - capture the list of deletion, and manually re-add them after the upgrade Neither solution is something I look forward too. --WjW