So can this bug be considered "sufficiently" fixed to move the fixed kaffeine to hardy-updates? Or should the update be pulled again, and a better fix be attempted?
So can this bug be considered "sufficiently" fixed to move the fixed kaffeine to hardy-updates? Or should the update be pulled again, and a better fix be attempted?