From owner-freebsd-questions Tue Feb 4 13:37:13 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C586E37B401 for ; Tue, 4 Feb 2003 13:37:10 -0800 (PST) Received: from tomts12-srv.bellnexxia.net (tomts12.bellnexxia.net [209.226.175.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id D487843F93 for ; Tue, 4 Feb 2003 13:37:09 -0800 (PST) (envelope-from pippo@bellnet.ca) Received: from pippo.bellnet.ca ([65.94.99.252]) by tomts12-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP id <20030204213707.DFUP1478.tomts12-srv.bellnexxia.net@pippo.bellnet.ca>; Tue, 4 Feb 2003 16:37:07 -0500 Message-Id: <5.1.0.14.2.20030204162836.00b71b48@pop51.bellnet.ca> X-Sender: lesp3999@pop51.bellnet.ca X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 04 Feb 2003 16:36:55 -0500 To: Kent Stewart From: pippo@bellnet.ca Subject: Re: portupgrading problems Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <200302040748.52149.kstewart@owt.com> References: <5.1.0.14.2.20030204093227.00b80788@mail.host45.com> <5.1.0.14.2.20030204093227.00b80788@mail.host45.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 07:48 AM 2/4/2003 -0800, you wrote: >On Tuesday 04 February 2003 07:00 am, pippo@bellnet.ca wrote: > > Some time ago I chose FreeBSD over all other *nix systems because I > > found the system better managed, easier to administrate, better > > supported and simpler to update and upgrade both the OS and the > > programs - especially through portupgrade. > > Several times I have encountered glitches in the update process; some > > I managed to figure out what the problem was, some other I just had > > to wait until the port was corrected then re-cvsup and portupgrade. > > This, on 2 similar FBSD v.4.7 installations. > > > > Currently I have encountered problems with updating KDE3 (because > > kdegames3 had some sort of problem - I don't have time for the games > > anyway, but this messes up the update - and the audio/arts program > > also had problems) and Openoffice 1.02. > >I think you have something else that is wrong. For example, if you check >the cvs-repository, nothing has been modified on kdegames since it was >updated to version 3.1 6 days ago. About 18 hours ago, I cvsuped >ports-all, rebuilt INDEX like you are supposed to do after cvsuping, >and then ran > >portupgrade -pufr qt > >This rebuilt all of the ports that depend on qt-3.1.1_2 and pretty much >includes all of kde and arts. > >What version are you trying to upgrade kde from? The older versions >basically require a package delete and fresh install. They also don't >work with XFree86-3.3.6. You have to use version 4.x. My usual procedure is this: cvsup -g -L 2 /usr/share/examples/cvsup/ports-supfile && portsdb -Uu I then check to see what is out of date and usually run portupgrade -ra If there are minor upgrades, things go pretty fast; otherwise I just let the machine go to it for hours during off hours for me.... Sometime, as I mentioned, things get screwed up - but why. Just now, on one machine kde would not update because of some "spelling problem" ??? that's a werd one - in the arts audio/arts port. To me, this means that there was either an error in the download or in the port (or port patch or whatever). Am I wrong? On the other machine, it was the kdegames3 that caused a problem... What would be the best way to correct the problem? Delete the files from the ports directory and run cvsup again? Or... ? >If a port requires to much space, then you need to use the prebuilt >packages. Ok, that's quite reasonable... sometimes it is difficult to find them :)) >Kent > > > Open office seems to be a particular case as it requires 4Gb of space > > for installation on *nix! I cannot think of another program that > > seems to be so bloated for installation. Is there an insurmountable > > problem here? I did find a port for FBSD to install the Ooo v.1.0.1 > > but now to update - whammo! It seems to me that it is rare that one > > needs the huge capacity disks that seem so current - I have 1 10gb > > and 1 34Gb raid array, but they are used for different OS's and for > > storage. It is impractical to have to re-organize your entire system > > just for 1 program. :(( > > > > If the port is faulty and is uploaded to the port site, then the > > downloaded port sits in the machine and then you have to figure out > > what went wrong. What is annoying is the enormous time it take to > > reinstall stuff like KDE3 and Open office only to find that the > > installation has failed and sometimes the old installarion is screwed > > up... Fortunately, I have not committed to using FBSD and the *nix > > program exclusively as, so far, I have found that there are still > > nasty kinks in the gears that take away too much time from creative > > productivity for maintenance > > > > Can someone explain the best way to deal with the updating process? > > How to minimize updating problems? > > Thanks in advance, > > PJ > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > >-- >Kent Stewart >Richland, WA > >http://users.owt.com/kstewart/index.html > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message