Yeah already preparing a fix. Turns out the fix from 3.4-1.1 was a
different fix from the one posted by the NMU'er on the bug. :-(

Reply via email to