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 debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to