[freebsd] portupgrade deki sorunlar..

[Mesut GÜLNAZ]

tam anlayamadım ama bu satırlarda ne demek istiyor.. bundan sonra release lerde hep bu sorunla karşılaşacak mıyız?  > > It could be a problem with the DBDriver. You could try this: > > Edit /root/.cs... > > and add > > PORTS_DBDRIVER=bdb1_hash > > PKG_DBDRIVER=bdb1_hash > Doesn't the DBDRIVER bug result in ruby dumping core? 'Cuz it isn't in this > case, it fails gracefully. The core dump is seen with portsdb(1) trying to create /usr/ports/INDEX.db -- however, the underlying bug can affect anywhere that ruby uses bdb1_btree files. pkgdb(1) occasionally going a bit funny is a problem that's been known about for some time; usually just deleting and rebuilding /var/db/pkg/pkgdb.db will sort things out. However, I don't think anyone had ever tracked down the root cause of the problem. Then the portsdb coredumping thing came along, and it seems an obvious conclusion that the same thing might be affecting both programs. Note that a fix for the bdb1_btree problem has been in HEAD for a few weeks, and was MFC'd to both RELENG_4 and RELENG_5 a week or so ago. So an alternative fix could be cvsup+buildworld. Unfortunately, I don't think the fix will be applied to any of the existing 4.x-RELEASE or 5.x-RELEASE branches -- it will of course be in 5.3-RELEASE when that comes out, and it's pretty easy to do if you want to patch things yourself. > I'll go ahead and try this, but I suspect that the /var/db/pkg info for > gnucash or one of it's dependancies got horked up. We'll see. > > > Then execute this in your shell also. Then do: > > pkgdb -u && portsdb -u && portupgrade -R gnucash