package corrupt/whats the "official" way of dealing with?

Achilleus Mantzios achill at matrix.gatewaynet.com
Mon Jun 5 07:16:18 PDT 2006


O Jack Raats έγραψε στις Jun 5, 2006 :

> The below commands will look at your packages files and compare the 
> checksums to find a corrupted file.
> It also will clean the ports/package directories from crap.
> It will NOT destroy any installed packages or port unless it's corrupted.
> It's very safe to use these commands.
> 
> You'll need to have root priveleges to run these commands of course

These commands have nothing to do with my problem.

-C cleans work dirs
-D(D) distfiles
-P(P) package tarballs
./distclean.sh cleans distfiles too

Any one else has any ideas?

> 
> JAck
> 
> 
> ----- Original Message ----- 
> From: "Achilleus Mantzios" <achill at matrix.gatewaynet.com>
> To: "Jack Raats" <jack at raats.org>
> Sent: Monday, June 05, 2006 10:48 AM
> Subject: Re: package corrupt/whats the "official" way of dealing with?
> 
> 
> O Jack Raats έγραψε στις Jun 5, 2006 :
> 
> > I once had a simular problem.
> > I solved it using the following commands after each other
> >
> > portsclean -C
> > portsclean -D
> > portsclean -DD
> > portsclean -P
> > portsclean -PP
> > cd /usr/ports/Tools/scripts
> > ./distclean.sh -f
> >
> > SUccess!
> 
> My problem post probably lies in the erroneous absence
> of +CONTENTS file in the problematic /var/db/pkg/<pkg name>/
> dirs.
> 
> Does any of the above commands you used affects/rebuilds those +CONTENTS
> files?
> 
> >
> > Jack Raats
> >
> >
> >
> > ----- Original Message ----- 
> > From: "Achilleus Mantzios" <achill at matrix.gatewaynet.com>
> > To: <freebsd-ports at freebsd.org>
> > Sent: Monday, June 05, 2006 10:20 AM
> > Subject: package corrupt/whats the "official" way of dealing with?
> >
> >
> > >
> > > 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
> > >
> > >
> > >
> > > _______________________________________________
> > > freebsd-ports at freebsd.org mailing list
> > > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > > To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
> > >
> > >
> >
> 
> 

-- 
-Achilleus




More information about the freebsd-ports mailing list