-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Susan Mackay wrote:
Thanks for the information. However, one answer leads to two questions:
1) what sort of time frame is "a short while" (days, weeks,....)
Half an hour normally. Then use `sudo port sync` to update your ports tree and to get the newest updates. Then run the command.
2) is there somewhere I can look to se if things like this have already been reported to same the 'noise' in the list? (I couldn't find anything in this list when I looked - perhaps it was under another title)
You can search Trac [1] to see if this bug was already reported. You can also search the mailinglist archive [2].
Thanks
Susan
Hope this helps, Simon [1]: http://trac.macports.org/projects/macports/search [2]: http://lists.macosforge.org/pipermail/macports-users/ - -- + privacy is necessary + using http://gnupg.org + public key id: 0x6115F804EFB33229 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGwaoBYRX4BO+zMikRCk0rAKCjfX1Z2BZJjMHsElv/V1WOqK/TNwCeIgTf Dp9kpxT6NUgteeFk+SvyHgI= =tzzK -----END PGP SIGNATURE-----