Presne tak. Zmazat portupgrade (napr. pkg_deinstall -fi portupgrade) a nainstallit ho znova, indexy mazat nie je treba (aspon ja som nemusel), ale kludne to pre istotu sprav.
G Ondra Koutek wrote: > Probiralo se to na konferenci ports. > je to bug v portupgrade a je potreba upgradovat na posledni verzi. > Pak smazat index a stahnout ho znova a melo by se to vzpamatovat. > Osobne jsem stale na cvs takze se me to netykalo (pouze jsem musel > odinstalovat portupgrade a nainstalovat to nove). > > Ondra > > Daniel DvoÅák pÃÅ¡e v pá 09. 02. 2007 v 11:48 +0100: >> Ahoj lidi, prosim poradte s portsnap. Provedl jsem po delsi dobe >> portsnap fetch update, portversion -vL= na nekolika ruznych serverech, >> to co nasledovalo nebylo vubec pekny a bylo to vsude stejny: >> >> portversion -vL= >> cd: can't cd to /usr/ports/sysutils/portupgrade >> [Updating the portsdb <format:bdb_btree> in /usr/ports ... - 16509 port >> entries found >> .........1000.........2000.........3000.........4000.........5000.........6000.........7000.........8000.........9000.........10000.........11000.........12000.........13000.........14000.........15000.........16000..... >> ..... done] >> [missing key: categories] [Updating the portsdb <format:bdb_btree> in >> /usr/ports ... - 16509 port entries found >> .........1000.........2000.........3000.........4000.........5000.........6000.........7000.........8000.........9000.........10000.........11000.........12000.........13000.........14000.........15000.........16000..... >> ..... done] >> missing key: categories: Cannot read the portsdb! >> database file error >> pak nasledoval bezny vypis zastaralych softu jako pred tim jako obvykle >> jako kdyz neni problem :) >> >> Setkal se s tim nekdo a co s tim jako mam delat ? >> >> DÃky >> Dan > -- FreeBSD mailing list ([email protected]) http://www.freebsd.cz/listserv/listinfo/users-l
