The bug seems to be fixed in dapper, which is why I think we can close this bug, but it's true I am not quite sure it is the policy. Can you reproduce this bug on dapper ?
It the problem arises only in breezy and is fixed in dapper, you should request a backport: see https://wiki.ubuntu.com/UbuntuBackports
The bug seems to be fixed in dapper, which is why I think we can close this bug, but it's true I am not quite sure it is the policy.
Can you reproduce this bug on dapper ?
It the problem arises only in breezy and is fixed in dapper, you should request a backport: /wiki.ubuntu. com/UbuntuBackp orts
see https:/