Portupgrade ruby problem

[bsd]

Mmmh...

I have followed your instructions and am still facing a problem :

root 0:34 ~ # portversion -l "<"
[Rebuilding the pkgdb <format:bdb_btree> in /var/db/pkg ...  
[Rebuilding the pkgdb <format:bdb_btree> in /var/db/pkg ...  
uninitialized constant PkgDB::BDB: Cannot update the pkgdb!]
Command failed [exit code 1]: /usr/local/sbin/pkgdb -aFQ

I can not rebuild the database using pkgdb -fu

root 0:37 ~ # pkgdb -fu
--->  Updating the pkgdb
[Rebuilding the pkgdb <format:bdb_btree> in /var/db/pkg ...  
uninitialized constant PkgDB::BDB: Cannot update the pkgdb!]


?? Any idea.


Le 3 juil. 06 à 10:48, Jacques S. a écrit :

> bsd wrote:
>> Hello,
>> I have a new problem that has just occured on my main mail server.
>> I am upgrading the ports on this server every two or three days  
>> using portsnap and portupgrade.
>> After portsnap has updated it's index I do a "portupgrade -arR" to  
>> upgrade all ports on the system.
>> Mutt needed an update so I did what I am doing every couple of  
>> days since more than one year :
>> # portsnap update
>> # portupgrade -arR
>> My system faithfully started to update it's ports then...
>>> -L/usr/local/lib -o pgpring  pgppubring.o pgplib.o  lib.o  
>>> extlib.o sha1.o  pgppacket.o ascii.o -lintl -liconv
>>> cc -I/usr/local/include -Wall -O -pipe -L/usr/local/lib -rpath=/ 
>>> usr/local/lib -L/usr/local/lib pgpewrap.c  -o pgpewrap
>>> defined symbol "db_version_4002"
>>> ** Command failed [exit code 1]: /usr/local/sbin/pkgdb -aFQ
>>> --->  Skipping 'mail/mutt'
>>> /libexec/ld-elf.so.1: /usr/local/lib/ruby/site_ruby/1.8/i386- 
>>> freebsd5/bdb.so: Undefined symbol "db_version_4002"
>>> /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:444:in `__system':  
>>> Command failed [exit code 1]: /usr/local/sbin/pkgdb -aFQ  
>>> (CommandFailedError)
>>>         from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:467:in  
>>> `__sudo'
>>>         from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:473:in  
>>> `xsystem!'
>>>         from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:960:in  
>>> `autofix!'
>>>         from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:956:in  
>>> `autofix'
>>>         from /usr/local/sbin/portupgrade:475:in `main'
>>>         from /usr/local/sbin/portupgrade:714:in `main'
>>>         from /usr/local/lib/ruby/1.8/optparse.rb:815:in `initialize'
>>>         from /usr/local/sbin/portupgrade:209:in `main'
>>>         from /usr/local/sbin/portupgrade:1951
>> I shooted portupgrade again but that did nothing, the donkey was  
>> stucked !!
>>> root 8:08 ~ # portupgrade -arR
>>> /libexec/ld-elf.so.1: /usr/local/lib/ruby/site_ruby/1.8/i386- 
>>> freebsd5/bdb.so: Undefined symbol "db_version_4002"
>> I have also try to reinstall "portupgrade" and "ruby18" that did  
>> nothing !!
>> Any idea of how to proceed...
>> Another interesting information :
>>> root 8:18 ~ # uname -a
>>> FreeBSD newmail.rmm.fr 5.4-RELEASE-p8 FreeBSD 5.4-RELEASE-p8 #0:  
>>> Thu Nov 24 16:34:35 CET 2005     root at newmail.rmm.fr:/usr/obj/usr/ 
>>> src/sys/GENERIC  i386
>> Thanks for your support.
>> ________________________________________________
>> «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§
>> ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
>> Gregober ---> PGP ID --> 0x1BA3C2FD
>> bsd @at@ todoo.biz
>> ________________________________________________
>> «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§
>> ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
>> _______________________________________________
>> freebsd-questions at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to "freebsd-questions- 
>> unsubscribe at freebsd.org"
>
> This worked for me:
> # cd /var/db/ports/portupgrade
> # rm options
>
> # cd /var/db/pkg
> # rm pkgdb.db
> # pkgdb -fu
>
> Discovered I had both ruby versions in ports: db4-4.x.x and db41-4.x.x
> I needed only db41; nothing depended (any more) on db4, so:
>
> # pkg_delete db4-4.x.x
>
> Note, I had migrated to WITH_BDB4=true, quite a long time ago.
>
> The recent tribulations with portupgrade has been on the list  
> already, several times, at several stages of the problem, and  
> various solutions have been described. Some of those seem more  
> complicated than this. I don't think the problem is complicated, at  
> least not in every case. At least not, now that the maintainer has  
> worked to fix the port.
>
> --
> Jacques S.
>

________________________________________________
«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Gregober ---> PGP ID --> 0x1BA3C2FD
bsd @at@ todoo.biz
________________________________________________
«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯