package corrupt/whats the "official" way of dealing with?
Achilleus Mantzios
achill at matrix.gatewaynet.com
Mon Jun 5 01:09:11 PDT 2006
Hi,
during a 6.0-BETA1 to 6.1-RELEASE-p1 upgrade cycle
and a subsequent
portupgrade -PRr '*',
(and most probably while doing the nvidia port),
my system crashed and it left the /var/db/pkg system
in a corrupted condition:
pkg_info: the package info for package 'apache-ant-1.6.5' is corrupt
pkg_info: the package info for package 'arts-1.4.2,1' is corrupt
pkg_info: the package info for package 'at-spi-1.6.4' is corrupt
pkg_info: the package info for package 'bitstream-vera-1.10_1' is corrupt
pkg_info: the package info for package 'bugbuddy-2.10.0_1' is corrupt
pkg_info: the package info for package 'cairo-0.4.0' is corrupt
pkg_info: the package info for package 'cvsup-16.1h_2' is corrupt
pkg_info: the package info for package 'dasher-3.2.15' is corrupt
pkg_info: the package info for package 'dri-6.2.1,2' is corrupt
pkg_info: the package info for package 'eclipse-3.1' is corrupt
pkg_info: the package info for package 'eel-2.10.1_1' is corrupt
pkg_info: the package info for package 'el-kde-i18n-3.4.2' is corrupt
pkg_info: the package info for package 'el-openoffice-1.1.5.rc2' is
corrupt
pkg_info: the package info for package 'eog-2.10.2' is corrupt
None of the popular -f -u etc... pkgdb switches seem to remedy the
problem.
What should i do?
I am thinking of deleting the above dirs and installing those packages
again.
--
-Achilleus
More information about the freebsd-ports
mailing list