Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 17 Jul 2004 11:26:39 +0200
From:      Guido Falsi <mad@madpilot.net>
To:        Kent Stewart <kstewart@owt.com>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: portupgrade error
Message-ID:  <20040717092639.GB18974@wedge.madpilot.net>
In-Reply-To: <200407161551.05456.kstewart@owt.com>
References:  <20040716184912.GA13209@wedge.madpilot.net> <200407161551.05456.kstewart@owt.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 16, 2004 at 03:51:05PM -0700, Kent Stewart wrote:
> On Friday 16 July 2004 11:49 am, Guido Falsi wrote:
> > Hello!
> >
> > I'm experiencing a strange erro message fro portupgrade:
> >
> > wedge# portupgrade -a
> > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in `deorigin': cannot
> > convert nil into String (PkgDB::DBError) from
> > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in `tsort_build' from
> > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each' from
> > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' from
> > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' from
> > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' from
> > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' from
> > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!' from
> > /usr/local/sbin/portupgrade:674:in `main'
> >         from /usr/local/sbin/portupgrade:207:in `initialize'
> >         from /usr/local/sbin/portupgrade:207:in `new'
> >         from /usr/local/sbin/portupgrade:207:in `main'
> >         from /usr/local/sbin/portupgrade:1845
> >
> > I've looked around the mailing list archives and tried all the
> > proposed solutions... rebuilding ruby and portupgrade from scratch,
> > deleting and rebuilding all ports and pkg related databases,
> > recvupping the ports tree from scratch(I have an empty refuse file).
> 
> This looks like the problem that portupgrade was having a while back. If 
> you can't portupgrade portupgrade, delete it and build it from scratch. 
> Ruby and been updated and you might as well start with it.

Already ried that multiple times, removing all portupgrade and ruby and
rebuilding them from scratch, but it keeps doing that.

Any other port that could have some influence I can try to rebuild?

I also tried defining RUBY_DEFAULT_VER=1.6 and rebuilding both from
scratch but nothing changed.

-- 
Guido Falsi <mad@madpilot.net>



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