severity 288262 important thanks Hi,
Does somebody still gets this issue with 2.0.4 ? Does somebody get the issue while updating from 1.0 ? I'm changing the severity to important since nobody has opened a such bug for 2.0.4. Is somebody getting this issue now to work with upstream on that ? Cheers, Sebastien Bacher -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
