OSS-Fuzz is a Continuous Fuzzing for Open Source Software. When a bug is found, it is filed on bugs.chromium.org instead of the upstream's bugzilla. If the bug at $URL is public, that means that the issue has been fixed in the upstream git repository, so when upstream does not add anything useful in that place, you can: 1) Check the range date when ClusterFuzz has detected that the issue has been fixed and dig into upstream git repository; 2) Check if upstream made a new release after the issue has been fixed; 3) Get in touch with upstream. See $URL for more details about the issue. @maintainer(s): after the bump, in case we need to stabilize the package, please let us know if it is ready for the stabilization or not.
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=889 https://gerrit.libreoffice.org/#/c/35325/ https://gerrit.libreoffice.org/gitweb?p=core.git;a=commitdiff;h=6e6e54f944a5ebb49e9110bdeff844d00a96c56c
This regression took place 1) one month after our current stable version was released 2) 3 days after the code freeze of our non-keyworded version and was fixed in git master 2 days later. Please stop wasting our time.
