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 wrote:
> This should tell you which one is problematic:
>
> for f in
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 whi
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 t
I've got a corrupted registry (receipts).
Will reinstalling macports correct a corrupted registry?
Is it possible to re-install macports from the .dmg while keeping all the
ports that are installed (and registered)?
How can I correct a corrupted registry, without re-installation?
Than