I can't reproduce this with 1:9.4.1-1, but I wasn't able to attribute
this to a particular upstream changelog entry.  Could you confirm that
this bug has indeed been fixed?  Thanks.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to