I found it. It turns out I was grabbing the port's dir non- recursively, so those extra files/* were not getting included and thats what that cryptic error meant.

-Bill


On Feb 11, 2008, at 9:39 AM, Rainer Müller wrote:
William Siegrist wrote:
I actually get 147 warnings now instead of what you got in the email... As far as I know, the linting is working. I dont maintain the lint code, I just maintain the server-side process for making those emails exactly from the output of "port lint". You should get the same errors locally with "port lint" before committing. If you see a discrepancy, definitely forward me the output the server gave you and the output you get locally.

Yes, locally I also get these 147 warnings and they are "unfixable" (the patches will be downloaded and therefore can't be named differently). But the port lint post-commit hook sent me this error message only.

Rainer





----
William Siegrist
Software Support Engineer
Mac OS Forge
http://macosforge.org/
[EMAIL PROTECTED]
408 862 7337





Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to