portsdb -Uu results in coredump

[Tim Kellers]

I'm trying it again, though this time it's on Yet Another 5.3gbeta2 machine.  
I'll try it again on a production 4.10-Stable machine in a few minutes.

Tim

On Monday 06 September 2004 01:11 am, Sahil Tandon wrote:
> Tim Kellers wrote:
> > I pkg_delete'd portupgrade and all of ruby, reinstalled portupgrade (and
> > all of ruby) and had to do a portsdb -Uu even after I did a make
> > fetchindex in /usr/ports to make the pkgdb in /var/db/pkg happy.  Since
> > I've done all of those things, portupgrade is working again.  I had to to
> > this on three machines --2 5.3 beta2 and one 4.10-STABLE, although on the
> > stable machine I managed to skip the portsdb -Uu step after the make
> > fetchindex step. Whatever broke the pkgdb did it around the 8500 number
> > port in the index.
>
> I'm having no such luck.  I've done the following:
>
> # pkg_delete -f portupgrade\*
> # pkg_delete -f ruby\*
> rmdir: /usr/local/share/ri/1.8/system: No such file or directory
> pkg_delete: unexec command for '/bin/rmdir -p
> /usr/local/share/ri/1.8/system' failed
> rmdir: /usr/local/share: Directory not empty
> pkg_delete: unexec command for '/bin/rmdir -p
> /usr/local/share/ri/1.8/site' failed
> pkg_delete: couldn't entirely delete package (perhaps the packing list is
> incorrectly specified?)
> # cd /usr/ports/sysutils/portupgrade/ ; make install clean
> # cd /usr/ports ; make fetchindex
> # portsdb -Uu
>
> ... and then I get the same ruby coredump after all that.  FWIW, I'm
> running 4.10-STABLE.  And I also encounter the error somewhere after the
>   8000th number port.
>
>
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"