Nice command line, Jeremy! I did find my own custom port had some \n chars in long_description that screwed up the registry. It's all working correctly now.
Phew! Thanks! On Wed, Apr 22, 2009 at 4:01 PM, Jeremy Huddleston <[email protected]>wrote: > This should tell you which one is problematic: > > for f in /opt/local/var/macports/receipts/*/*/receipt.bz2; do echo -n $f && > bzcat $f | wc -l; done | grep -v ' 2$' > > > > On Apr 22, 2009, at 14:09, Rainer Müller wrote: > > Darren Weber wrote: >> >>> I've got a corrupted registry (receipts). >>> >> >> Do you know which receipt it is? >> >> I assume this the issue with using \n in the >> description/long_description as you did in your gdb port. In this case, >> you could fix it by editing the receipt by hand. A valid receipt should >> have only two lines. The first is the version number, the second one >> contains all the information about the port. >> >> If there was some \n in the description/long_description, these new >> lines are written into this receipt file as actual new lines. So, to get >> a working receipt again, remove the new lines by joining these lines to >> a single one. >> >> You will find the receipt at >> /opt/local/var/macports/receipts/<name>/<composite_version>/receipt.bz2 >> >> These are compressed, but plain text. Uncompress, edit and compress >> again (or if you know vim, it will do it automatically for you). >> >> If my guess above was wrong, please show the receipt file in question >> and describe what you did. >> >> Rainer >> _______________________________________________ >> macports-users mailing list >> [email protected] >> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users >> > >
_______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
