From owner-freebsd-stable Thu Jan 25 5:33:27 2001 Delivered-To: freebsd-stable@freebsd.org Received: from www.golsyd.net.au (ftp.golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id 18AE337B401 for ; Thu, 25 Jan 2001 05:33:10 -0800 (PST) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AH9370.63.d1acf55c) with ESMTP id cawsaaaa for ; Fri, 26 Jan 2001 00:41:47 +1100 Message-ID: <3A702B20.EBEE505@quake.com.au> Date: Fri, 26 Jan 2001 00:33:20 +1100 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Dmitry Karasik Cc: freebsd-stable@freebsd.org Subject: Re: Ports update - is something broken? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitry Karasik wrote: > > Hi! > > I recently cvsupped the ports tree on my 4.1-stable, but after that > make refused to deal with ports - 'Your system is too old to use this > bsd.port.mk.'. I believed that ports update procedure should be more or > less aware of current version, and do not fetch files that force to > buildworld the whole system - but that is just because I never had that kind of > situation before. Could anyone explain what happened, or at least point > to the relevant piece of documentation? man cvsup either is not enough or > is too obscure... I think you will find cvsup didnt remove some of the old stuff in your ports tree... A simple solution if you have the time is to rm -rf your ports and cvsup them again... Im sure there is a more elegant solution, check the mail archives, this has been discussed at least twice before... Good luck! Kal. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message