From owner-freebsd-stable Wed Jan 15 10:54:18 2003 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A8AB37B405 for ; Wed, 15 Jan 2003 10:54:16 -0800 (PST) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5640943E4A for ; Wed, 15 Jan 2003 10:54:15 -0800 (PST) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP id MUA74016; Wed, 15 Jan 2003 10:54:14 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id B11235D04; Wed, 15 Jan 2003 10:54:14 -0800 (PST) To: Pierrick Brossin Cc: Belphoebe Niressi , freebsd-stable@FreeBSD.ORG Subject: Re: Portversion - Portupgrade In-reply-to: Your message of "Sun, 12 Jan 2003 13:12:35 +0100." <3E215BB3.9020400@swissgeeks.com> Date: Wed, 15 Jan 2003 10:54:14 -0800 From: "Kevin Oberman" Message-Id: <20030115185414.B11235D04@ptavv.es.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Date: Sun, 12 Jan 2003 13:12:35 +0100 > From: Pierrick Brossin > Sender: owner-freebsd-stable@FreeBSD.ORG > > Belphoebe Niressi wrote: > >>Running 4.7 and having problems to upgrade my system. > > > > *points at -questions* you're running 4.7, not STABLE. > > Oops choosed the wrong address sorry! > > >>Did it but my system doesnt get updated. I get errors when it tries > > > > > > man portupgrade will tell you how to skip certain ports. > > > > You can then rebuild those explicitly and, unlike how > > Zebras and Aardvarks and everything in between entered > > the Ark, one by one. > > I think I will simply use the old method which is to update > the ports one by one... > I thought portupgrade was to update the ports on my system but > actually it's not working well... > > > Also, ask yourself this question: Is there a reason I > > am upgrading? > > Sure I've been using this system for quite a 'long' time now > and I have bugs in many apps that are in the 'to be upgrade' list.. Trying to keep complex things like gnome in sync without portupgrade is nearly impossible. I have never had serious problems with it since its earliest days when it was added to the ports tree before the author was really ready for it to be released. Even then, it was a winner. READ THE MAN PAGE! You were doing 'portupgrade -a'. You probably didn't want to do this. You probably wanted to do a 'portupgrade -Rra' to graph all dependencies and rebuild everything in the proper sequence. If the system is old and has had many ports on it through many versions, I would suggest cleaning up your system by de-installing all ports and packages and deleting most everything in /usr/local. BACKUP /usr/local FIRST!! You may have some things in /usr/local/etc, /usr/local/bin and /usr/local/lib that you want to save, but there should not be much. /usr/local/include should be cleaned up, as it can cause all kinds of odd problems when old files are left around for the compiler to find. This is time consuming, but, with the help of portupgrade, your system will not get cluttered with old cruft, so you will only have to do it once. Then install the portupgrade port. Edit /usr/local/etc/pkgtools.conf to include any special build instructions for any port. Then use portinstall to re-install the ports you need. Once this is done you should be able to keeps port current by: cvsup (Update the ports tree) portsdb -Uu (Rebuild ports and packages databases to reflect changes in tree) portversion -vL= (List ports needing updates. portupgrade -Rr portupgrade (only if portupgrade is in the list from portversion) portupgrade -Rra (Upgrade EVERYTHING!) (Did I mention that you need to read the man page carefully?) R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message