Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 2 Mar 2003 00:12:04 -0500
From:      taxman <taxman@acd.net>
To:        Cliff Sarginson <cls@willow.raggedclown.intra>, FreeBSD Questions <FreeBSD-questions@FreeBSD.org>
Subject:   Re: Portupgrade -- am not Einstein
Message-ID:  <200303020012.04749.taxman@acd.net>
In-Reply-To: <20030301235345.GA5423@willow.raggedclown.intra>
References:  <20030301235345.GA5423@willow.raggedclown.intra>

next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 01 March 2003 06:53 pm, Cliff Sarginson wrote:
> Ok,
> I give in.
>
> /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:310:in `deorigin': failed to
> convert nil into String (Pkg DB::DBError)
>
> After most of two days trying to understand portupgrade, RTFM, and advice
> given on this list, I give in.
>
> Trying to upgrade KDE .. totally hopeless.
> "arts" won't build...therefore kdelibs won't build.

Well it looks like you've done everything right, but building that large of a 
port is not perfect.  It depends on so many pieces to be right that any 
changes can bork it pretty good.  Or really just any little extra stuff left 
over in your build environment can screw it up.
Only way I get KDE to upgrade sometimes (I've done it 6 times or so) is to 
build it from scratch with no other ports installed.  This may not be 
realistic given your system, so try using a testbox.  Install from scratch, 
cvsup ports and let it build away on 
portupgrade -Np kde-3.1 
That will make packages for you that you can then install on your other 
systems.  Option 2 is to download packages.  fruitsalad.org is a project run 
by some of the people doing kde on freebsd, and they have kde packages for 
FreeBSD.  Option 3 is to learn how to set up jails, and do the above build 
from scratch inside of a jail and then install the packages that result onto 
the original system.
KDE including all of the dependencies took 8-9 hrs to build on my Duron 700 
with slow discs.  So I'd try that, go do something else for the day and save 
what hair you have left  :)

Tim




> The last straw was the above error message.
> I presume it means something to somebody.
>
> Well, I know it is a wonderful tool.
> But I have given up on it.
> I am unable to re-instate the status quo with KDE via FTP, since
> No FTP server understands 4.8-PRERELEASE.
>
> Setting the release option as "any" does nothing worthwhile.
> And as for the recursive -R/r options.. they seem to be working on their
> own agenda. It was actually quite easy to upgrade X, by just doing it
> through the "normal" ports mechnism. Portupgrade made it into a pig's
> breakfast.
>
> And why on earth is portupgrade arts, looking for things in
> /usr/local/lib/.libs ?
>
> Mmm.
>
> I was my belief that the ports were independent from the release.
> This is not the case. Why is there a 4.8-PRERELEASE ports section ?
>
> I followed all the bouncing balls. But they have defeated me.
>
> I was trying to update X11/KDE. Not a chance.
>
> I think, that if a port reflects a new version of something so massive
> as X/KDE/Gnome, it should not be let loose until a binary package update
> is available for it.
>
> My understanding may be wrong. But I accept the 'cutting' edge aspect of
> tracking Stable as regards the base system..which actually is in my
> experience almost *never* a problem. But tracking ports is a very
> hazhardous task, especially with meta-ports.
>
> I really think some clarification is needed on this.
>
> And why Ruby ? Why on earth is something like a fundamental tool written in
> a language whose widespread use is noticeable by it's absence.
>
> I really have read the documents, and read the mailing list advice.
> But..sheesh..
>
> Ah well...no flames please. Sound advice, slaps on the wrist..fine.
> But it has got me beat..


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200303020012.04749.taxman>