Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 18 Oct 2011 17:13:37 -0400
From:      Wesley Shields <wxs@FreeBSD.org>
To:        Leslie Jensen <leslie@eskk.nu>
Cc:        Matthias Andree <matthias.andree@gmx.de>, freebsd-ports@freebsd.org
Subject:   Re: What is wrong here?
Message-ID:  <20111018211337.GF91604@atarininja.org>
In-Reply-To: <4E9C8E70.3090503@eskk.nu>
References:  <4E9C8B9E.6080801@eskk.nu> <4E9C8C86.4060401@gmx.de> <4E9C8E70.3090503@eskk.nu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 17, 2011 at 10:22:08PM +0200, Leslie Jensen wrote:
> 
> 
> 2011-10-17 22:13, Matthias Andree skrev:
> > Am 17.10.2011 22:10, schrieb Leslie Jensen:
> >>
> >> I have a script that does
> >>
> >> portsnap fetch update
> >>
> >> pkg_version -vIL=
> >>
> >> on a Daily basis
> >>
> >>
> >> Today I got this little message about "corrupted record" and I would
> >> like to solve it
> >>
> >>
> >> ImageMagick-6.7.3.0_1<    needs updating (index has 6.7.3.1)
> >> pkg_version: corrupted record (pkgdep line without argument), ignoring
> >> pkg_version: corrupted record (pkgdep line without argument), ignoring
> >> kdemultimedia-4.6.5<    needs updating (index has 4.7.2)
> >> libgtop-2.28.3_1<    needs updating (index has 2.28.3_2)
> >>
> >>
> >> Any suggestions?
> >
> > It might help to run:
> >
> > portmaster --check-depends
> >
> > and the corruption is either from a file system corruption (like: hard
> > shutdown/power blackout with enabled write caches), or from an
> > interrupted portmaster/portupgrade/portinstall or "bare-bones" ports
> > make run.
> > _______________________________________________
> > freebsd-ports@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
> 
> 
> Thanks.
> 
> I have done that and I have two errors considering kdelibs-4.
> 
> At the moment kdelibs-4 will not build.
> 
> Because I deleted kdelibs following the instructions in UPDATING, that 
> might cause the error.
> 
> I didn't connect those two because there was no mention of port name in 
> the error.
> 
> Thanks for clarifying :-)

You can find out which pkg is giving you the problems by looking for
"@pkgdep " in /var/db/pkg/*+CONTENTS. If you find any lines with nothing
after the space then that is your problem. You should just be able to
rebuild that port or reinstall the package and you should be fine.

-- WXS



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111018211337.GF91604>