Both issues share the same fixing commit, although different, so still
we can track it under the same Debian bug.