From owner-freebsd-ports@FreeBSD.ORG Wed Aug 27 23:45:13 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 30BF017B for ; Wed, 27 Aug 2014 23:45:13 +0000 (UTC) Received: from smtp5.cc.ksu.edu (smtp-feca09d8910ed08e5e479c79aac3e744.cc.ksu.edu [129.130.255.125]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 05DA83BF9 for ; Wed, 27 Aug 2014 23:45:12 +0000 (UTC) Received: from mew.cns.ksu.edu (mew.cns.ksu.edu [129.130.0.181]) by smtp5.cc.ksu.edu (8.14.3/8.14.3) with ESMTP id s7RNdbHE004882 for ; Wed, 27 Aug 2014 18:39:38 -0500 (CDT) Message-ID: <53FE6C38.5070508@ksu.edu> Date: Wed, 27 Aug 2014 18:39:36 -0500 From: "Lawrence K. Chen, P.Eng." Organization: Kansas State University - ITS/Enterprise Server Technologies User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: I want to upgrade an old (8.3-RC2) FReeBSD installation, but can't install subversion References: <53FCF9D5.6030904@sorbs.net> <53FD3ED7.9030506@freebsd.org> <53FD87CD.7040006@dan.me.uk> <53FD9642.3020807@sorbs.net> <20140827163817.4645e67d@bsd64.grem.de> <20140827150741.GO9400@home.opsec.eu> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.98.4 at cts-virus1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.72 on 129.130.255.119 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Aug 2014 23:45:13 -0000 On 08/27/14 17:09, Torfinn Ingolfsen wrote: > Hello, > > On Wed, Aug 27, 2014 at 5:07 PM, Kurt Jaeger wrote: >> Hi! >>> I didn't figure it out from the man page at least. >>> Trying the simple solution doesn't work: >>> root@kg-vm2# freebsd-update fetch >> >> Try >> >> freebsd-update -r 8.4-RELEASE upgrade > > this one appears to work (and yes, I should have figured it out from > the man page): > root@kg-vm2# freebsd-update -r 8.4-RELEASE upgrade > Looking up update.FreeBSD.org mirrors... 5 mirrors found. > Fetching metadata signature for 8.3-RC2 from update5.freebsd.org... done. > Fetching metadata index... done. > Fetching 1 metadata files... done. > Inspecting system... done. > > The following components of FreeBSD seem to be installed: > kernel/generic src/base src/bin src/cddl src/contrib src/crypto src/etc > src/games src/gnu src/include src/krb5 src/lib src/libexec src/release > src/rescue src/sbin src/secure src/share src/sys src/tools src/ubin > src/usbin world/base world/doc world/games world/lib32 world/manpages > > The following components of FreeBSD do not seem to be installed: > world/catpages world/dict world/info world/proflibs > > Does this look reasonable (y/n)? y > > Fetching metadata signature for 8.4-RELEASE from update5.freebsd.org... done. > Fetching metadata index... done. > Fetching 1 metadata patches. done. > Applying metadata patches... done. > Fetching 1 metadata files... done. > Inspecting system... done. > Fetching files from 8.3-RC2 for merging... done. > Preparing to download files... done. > Fetching 34433 patches.....10....20....30....40....50....60....70....80....90....100....110....120.... > > > So perhaps the freebsd-update method should be documented as "the way out"? > I missed the start of this thread....but two months ago, had a customer with a FreeBSD 9.0 system (with jails) that had wanted to upgrade Jenkins ... where after doing an 'ezjail-admin update -P' ran into similar issues from bsd.port.mk. Using freebse-update to upgrade to 9.1-RELEASE went a lot better than I expected, including upgrading the jails...something its previous admin had said wasn't possible, hence the lack of updates/upgrades. At the time, I was partly hoping that 9.3 would make an early appearance, even though it would be difficult to know if there would be any surprises....beyond the ones I had prepared for, having run into such issues when I updated some servers from 9.1 to 9.2. But, I opted to only take them to 9.1, since at the time...9.2 was going to EOL at the end of September, while 9.1 wouldn't EOL until the end of the year. And, I had been told that they're moving sometime next quarter, so it'll be somebody else's problem when they need to upgrade again. Not sure about the fate of the other two production 9.1 servers. -- Who: Lawrence K. Chen, P.Eng. - W0LKC - Sr. Unix Systems Administrator For: Enterprise Server Technologies (EST) -- & SafeZone Ally