Date: Sun, 12 Feb 2017 12:27:44 +0100 From: Matthias Andree <matthias.andree@gmx.de> To: freebsd-ports@freebsd.org Subject: Re: Question on upgrading ports after 9.3->10.3 Message-ID: <ecfa95d0-97af-4caf-0a9d-0372b313dd9c@gmx.de> In-Reply-To: <alpine.BSF.2.20.1702121349541.46495@aneurin.horsfall.org> References: <alpine.BSF.2.20.1702121349541.46495@aneurin.horsfall.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 12.02.2017 um 04:05 schrieb Dave Horsfall: > Me again :-) I finally got around to following the notes that David=20 > Wolfskill kindly provided (thanks!) and apart from some oddity about=20 > "httpd" requiring a missing "libdb-4.2.so.2" (which will get rebuilt=20 > anyway), I'm a bit wary of this: The underlying assumption of all upgrade instructions also is that you start from a fully updated "old" system, i. e. 9.3-RELEASE-pwhatever (some p>50 IIRC) plus fully updated ports as of 9.3, as of "just before EOL", i. e. 2016-12-31, possibly with the 2016Q4 ports branch rather than head. If something requires libdb-4.2.so.2, then you haven't seen to your system since summer (northern hemisphere) 2014, and expect things to break. It may be easier to backup configuration and user data, and rebuild a new system from scratch in your situation. Note that I'd removed Berkeley DB 4.2 from FreeBSD's ports tree 2=BD year= s ago, exactly 2014-08-21T22:50Z, leaving only 4.8 and newer at the time. <https://svnweb.freebsd.org/ports?view=3Drevision&revision=3D365599>, and= running a web server that you haven't updated in 27 months is *not* considered good practice. Please plan sufficient time to maintain your software and install security updates thoroughly.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ecfa95d0-97af-4caf-0a9d-0372b313dd9c>