From owner-freebsd-ports@FreeBSD.ORG Wed Jul 4 00:09:36 2007 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B753316A400; Wed, 4 Jul 2007 00:09:36 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 929A713C45D; Wed, 4 Jul 2007 00:08:34 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 90E90E87; Tue, 3 Jul 2007 19:08:33 -0500 (CDT) Date: Tue, 3 Jul 2007 19:08:33 -0500 To: budsz Message-ID: <20070704000833.GA20506@soaustin.net> References: <4d4dc3640707021628p7dc9e2aan1e9d145cadb7407c@mail.gmail.com> <4689F9DA.6010302@FreeBSD.org> <4d4dc3640707030654n8a64f9aj8ed3f882fe11391a@mail.gmail.com> <468A5F08.2080907@FreeBSD.org> <4d4dc3640707030919q5966b568r8a51b06ef29f9c7d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4d4dc3640707030919q5966b568r8a51b06ef29f9c7d@mail.gmail.com> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: freebsd-ports@freebsd.org, Sergey Matveychuk Subject: Re: make fetchindex failure X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2007 00:09:36 -0000 On Tue, Jul 03, 2007 at 11:19:04PM +0700, budsz wrote: > So the best way I should upgrade my system to FreeBSD 6.X series?, Yes, that is what we have been recommending for some time now. > BTW which one: > > "tag=RELEASE_4_EOL" or "tag=RELEASE_4" ?, I've already read in > handbook and didn't find exactly "tag=RELEASE_4_EOL" :-( There was a README posted to ports@ about how to do this. OTOH if you have already upgraded your ports past the RELEASE_4_EOL point, then your best choice is to just go ahead and upgrade to 6.2. Otherwise, you are going to have to revert your ports tree and then deal with the fallout of having any ports you have upgraded since the RELEASE_4_EOL tag was laid down, and that would be a complete waste of time. mcl