Date: Tue, 8 Sep 2015 23:06:02 +0200 From: Rainer Duffner <rainer@ultra-secure.de> To: "Michael B. Eichorn" <ike@michaeleichorn.com> Cc: "Michael R. Wayne" <freebsd07@wayne47.com>, freebsd-stable@freebsd.org Subject: Re: pkg does bad things after upgrade from 8.4 to 9.3 Message-ID: <7A1CD302-0428-4068-ACD9-146C5E03802E@ultra-secure.de> In-Reply-To: <1441745722.12994.59.camel@michaeleichorn.com> References: <20150908175303.GP23144@manor.msen.com> <1441745722.12994.59.camel@michaeleichorn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 08.09.2015 um 22:55 schrieb Michael B. Eichorn = <ike@michaeleichorn.com>: >=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).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7A1CD302-0428-4068-ACD9-146C5E03802E>