ehm the "5.2.18" is not really fixing this bug, just the changelog entry from debian had reference for it :) anyway, working too, the hash is correct, so setting back to "verification-done"
ehm the "5.2.18" is not really fixing this bug, just the changelog entry from debian had reference for it :)
anyway, working too, the hash is correct, so setting back to "verification-done"