Comment 1 for bug 354505

Revision history for this message
Jonathan B. Wiebe (jbwiebe) wrote :

I notice that this is now fixed in version 1:1.6a-2

Thanks everyone!