Re: pkg_version: corrupted record (pkgdep line without argument), ignoring
On 10/22/11, b. f. bf1...@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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
pkg_version: corrupted record (pkgdep line without argument), ignoring
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. -- Jerry ✌ jerry+f...@seibercom.net Disclaimer: off-list followups get on-list replies or ignored. Do not CC this poster. Please do not ignore the Reply-To header. http://www.catb.org/~esr/faqs/smart-questions.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: pkg_version: corrupted record (pkgdep line without argument), ignoring
On Thu, Oct 20, 2011 at 3:20 PM, Jerry je...@seibercom.net 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. -- Jerry ✌ jerry+f...@seibercom.net Hi Jerry, Have you tried this : # portmaster --check-depends # portmaster -Da Source : http://www.cyberciti.biz/faq/pkg_version-corrupted-record-pkgdep-line-without-argument-ignoring/ You can have a look on this thread, where Doug Barton (portmaster's author) explain another way to resolve this problem. http://groups.google.com/group/lucky.freebsd.ports/browse_thread/thread/e2054d1cfadc0e3a/66c038dfffb36d40?lnk=raotpli=1 Regards, Alexandre ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: pkg_version: corrupted record (pkgdep line without argument), ignoring
On Thu, Oct 20, 2011 at 04:24:19PM +0200, Alexandre thus spake: On Thu, Oct 20, 2011 at 3:20 PM, Jerry je...@seibercom.net 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. -- Jerry ✌ jerry+f...@seibercom.net Hi Jerry, Have you tried this : # portmaster --check-depends # portmaster -Da Source : http://www.cyberciti.biz/faq/pkg_version-corrupted-record-pkgdep-line-without-argument-ignoring/ You can have a look on this thread, where Doug Barton (portmaster's author) explain another way to resolve this problem. http://groups.google.com/group/lucky.freebsd.ports/browse_thread/thread/e2054d1cfadc0e3a/66c038dfffb36d40?lnk=raotpli=1 Try looking into reporting pkgs from the output of this too: #!/bin/sh grep -A1 ^@pkgdep $ /var/db/pkg/*/+CONTENTS -jgh -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
pkg_version: corrupted record (pkgdep line without argument), ignoring
After attempting to use portmaster to update the KDE port, I am receiving repeated error messages when running the command: pkg_version -vIL= The error message: pkg_version: corrupted record (pkgdep line without argument), ignoring I am at a lost as to how to correct this problem. -- Carmel ✌ carmel...@hotmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: pkg_version: corrupted record (pkgdep line without argument), ignoring
Carmel schreef: After attempting to use portmaster to update the KDE port, I am receiving repeated error messages when running the command: pkg_version -vIL= The error message: pkg_version: corrupted record (pkgdep line without argument), ignoring I am at a lost as to how to correct this problem. run portmaster --check-depends. You will find the dependencies that no longer exist. regards Johan Hendriks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: pkg_version: corrupted record (pkgdep line without argument), ignoring
On Wed, 19 Oct 2011 13:58:45 +0200 Johan Hendriks articulated: Carmel schreef: After attempting to use portmaster to update the KDE port, I am receiving repeated error messages when running the command: pkg_version -vIL= The error message: pkg_version: corrupted record (pkgdep line without argument), ignoring I am at a lost as to how to correct this problem. run portmaster --check-depends. You will find the dependencies that no longer exist. I did that but it failed to correct the problem. I am now running pkgdb -L. When it completes I will see if the problem still exists. -- Carmel ✌ carmel...@hotmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
