Hi, I'll take a look at this, but it's unlikely I'll find a solution very soon. Upstream doesn't have a lot of time right now, and I'm not an expert in the codebase (though sometimes I do get lucky).
I think that it's probably best for you to fix your FTBFS by removing pychecker from debian/rules temporarily. You can put it back when the bug is fixed. Maybe we should clone 406347? You can fix your FTBFS by removing pychecker from debian/rules, and I'll keep this bug against pychecker open until we can figure out the problem. That way, the severity for the pychecker bug can be set to normal (which is more appropriate since AFAIK you're the only affected user), and users won't have any problem building your package in the meantime. Let me know what you think. KEN -- Kenneth J. Pronovici <[EMAIL PROTECTED]> http://www.cedar-solutions.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
