Date: Sat, 22 Oct 2011 21:59:00 -0400 From: "b. f." <bf1783@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: pkg_version: corrupted record (pkgdep line without argument), ignoring Message-ID: <CAGFTUwOnw94h0o5yAQFQ5wp2R%2BvB%2BzypT56Na2_%2BxjXne09jMA@mail.gmail.com> In-Reply-To: <CAGFTUwPsi0W7VCH-_gcr62YCzF7%2BKJLWL_FupsNXZ7v9=ff8pQ@mail.gmail.com> References: <CAGFTUwPsi0W7VCH-_gcr62YCzF7%2BKJLWL_FupsNXZ7v9=ff8pQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/22/11, b. f. <bf1783@googlemail.com> wrote: > Jerry wrote: >> After attempting unsuccessfully to update KDE4 via "portmaster", I >> found a number of errors printed out when using "pkg_version-vIL=". >> >> I eventually used "portmanager" to update the KDE4 port successfully; >> however, I am still receiving the following error messages. >> >> These ports need updating: >> pkg_version: corrupted record (pkgdep line without argument), ignoring >> pkg_version: corrupted record (pkgdep line without argument), ignoring >> pkg_version: corrupted record (pkgdep line without argument), ignoring >> koffice-kde4-2.3.3_3 < needs updating (index has >> 2.3.3_5) >> postgresql-client-8.2.21 < needs updating (index has >> 8.2.22_1) >> >> I have not found a way to ascertain which ports contain the corrupted >> records. Originally, there were over a dozen of them but "portmanager" >> fixed most of them for me. How can I determine what ports are still >> damaged so that I might correct them. > > As the others have written, you could use sed, grep, or visual > inspection to examine the pkgdb. Alternatively, you could try testing > one port at a time, to see what ports pkg_version chokes on, by using > something like: > > pkg_info -aE | xargs -tI @ pkg_version -vIL= -s @ Bah, sent this to freebsd-ports by mistake. Sorry. b.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGFTUwOnw94h0o5yAQFQ5wp2R%2BvB%2BzypT56Na2_%2BxjXne09jMA>