From owner-freebsd-stable@freebsd.org Tue Sep 8 21:10:05 2015 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 B426B9CCD8E for ; Tue, 8 Sep 2015 21:10:05 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from mail.ultra-secure.de (mail.ultra-secure.de [88.198.178.88]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F374113B8 for ; Tue, 8 Sep 2015 21:10:04 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (qmail 62317 invoked by uid 89); 8 Sep 2015 21:06:04 -0000 Received: from unknown (HELO ?192.168.1.200?) (rainer@ultra-secure.de@217.71.83.52) by mail.ultra-secure.de with ESMTPA; 8 Sep 2015 21:06:04 -0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: pkg does bad things after upgrade from 8.4 to 9.3 From: Rainer Duffner In-Reply-To: <1441745722.12994.59.camel@michaeleichorn.com> Date: Tue, 8 Sep 2015 23:06:02 +0200 Cc: "Michael R. Wayne" , freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <7A1CD302-0428-4068-ACD9-146C5E03802E@ultra-secure.de> References: <20150908175303.GP23144@manor.msen.com> <1441745722.12994.59.camel@michaeleichorn.com> To: "Michael B. Eichorn" X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Sep 2015 21:10:05 -0000 > Am 08.09.2015 um 22:55 schrieb Michael B. Eichorn = : >=20 >=20 >=20 > But you must reinstall everything. You upgraded your ABI going 8->9 so > everything needs rebuilt/reinstalled. See next. >>=20 Exactly. Or unpack the compat8x package by hand. Or don=E2=80=99t delete the old libraries upon upgrading=E2=80=A6 >>=20 >=20 > There is pkg-lock(8) but dont do it. You really need to upgrade it all > for a major version change. >=20 The valid use-case for pkg-lock is (IMO) if you want to downgrade. I follow the quarterly cuts of the ports-tree and build my own repo. If I need to downgrade from Q3 to Q2, I usually lock pkg only and do a = pkg upgrade -f The lock =E2=80=9Esurvives=E2=80=9C even the -f. The previous pkg may have problems reading the new pkg database created = by the new pkg=E2=80=A6. Locking anything else besides pkg is just a way to get unhappy. If you have more than a handful machines or are not content with the = packages provided by FreeBSD, running your own repo is a must IMO. For our Ubuntu and CentOS-servers at work, we don=E2=80=99t do the = builds ourselves - but we still run our own mirror that is updated at = our own schedule (so that servers are on a defined patch-level).