Hi there, This issue was originally reported against version 1:1.1.10-3. It was reported fixed two days ago in version 1:1.1.0-2 which makes no sense to me considering that oldstable is 1.1.8-5 and stable/unstable is 1.1.10-3. I'm still seeing this issue this morning. Thanks!
Tony -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
