You beat me to it Micah. :) On 8/19/06, Micah Anderson <[EMAIL PROTECTED]> wrote:
I just updated all my packages in unstable to the latest, and I do not experience this issue.
I also upgraded my packages in unstable to the latest, which included installing python2.4 for the first time, and I had no problems with bittornado afterwards. I also tried uninstalling python2.3 (still worked fine), and then uninstalling and reinstalling bittornado with only python2.4 present (still no problem). Artur, what install order did you use? I assume something like: first python2.3 (long ago), then bittornado (a while ago), then python2.4 (recently)? If that's the case you might try uninstalling/reinstalling bittornado to see if it solves your problem. As Micah asked, the output of dpkg -l "python*" might be helpful. Also, perhaps the output of "locate -e BitTornado". Cameron Dale -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
