FreeBSD Port: sysutils/portupgrade

[KOMATSU Shinichiro]

Hello,

Thank you for reporting, but I cannot determine
where the source of the trouble exists,
so whould you try the followings, please?

1. Try to add "--ignore-moved" option to portversion.
    With this option added, portversion totally ignores MOVED.

    I know some problems still remain in MOVED tracing function,
    so always try "--ignore-moved" if you encounter a problem.

2. Once remove INDEX.db and remake it by "portsdb -u".

3. If you set "PORTS_DBDRIVER" environment variable,
    try to unset it, remake pkg.db and INDEX.db,
    and see whether the same problem occurs.
    I did not test other than the default BDB version (BDB1).


Mike Jakubik wrote:
> It seems that there is something wrong with the new portupgrade. I 
> recently updated to 2.0.1,1 and i am experiencing freezes, which seems 
> to me caused by ruby sitting and taking up all cpu. I reinstalled all 
> decencies to be sure its a clean install, but the problem remains.
> 
> root at fbsd.local:~# pkgdb -F
> --->  Checking the package registry database
> [Rebuilding the pkgdb <format:dbm_hash> in /var/db/pkg ... - 214 
> packages found (-0 +214) 
> ....................................................................................................................................................................................................................... 
> done]
> root at fbsd.local:~# portversion -v
> [Updating the portsdb <format:dbm_hash> in /usr/ports ... - 13959 port 
> entries found 
> ..........1000.........2000.........3000.........4000.........5000.........6000.........7000.........8000.........9000.........10000.........11000.........12000.........13000......... 
> ...... done]
> BitchX-1.1                  =  up-to-date with port
> 
> ..... it sits here.
> 
> PID USERNAME      THR PRI NICE   SIZE    RES STATE    TIME   WCPU COMMAND
> 98156 root            1 125    0 26784K 26220K RUN      5:13 98.14% ruby18
> 
> 
> portupgrade-2.0.1,1 FreeBSD ports/packages administration and management 
> tool s
> ruby-1.8.2_5,1      An object-oriented interpreted scripting language
> ruby18-bdb4-0.5.7   Ruby interface to Sleepycat's Berkeley DB revision 2 
> or lat
> db4-4.0.14_1,1      The Berkeley DB package, revision 4
> db43-4.3.29         The Berkeley DB package, revision 4.3
> 
> Could it be a BDB conflict? 4.3 is required by cyrus imap.
> 
>