Add s3ql issue

There is no CVE yet, but one has been requested. It was proposed to
ingore the issue, but no confirmation from maintainer yet. The fix is
straightforward, but the fix needs a bump of the filesystem revision
number, making a filesystem created after the patch, not anymore
readable with unpatched s3ql versions.