On Fri, 2017-02-10 at 13:55 +0100, Michael Stahl wrote:
i wonder why they even show up, i thought workdir/UnpackedTarball was
excluded from the scan?
It used to be, but I migrated away from building everything and then
filtering out stuff to ignore towards building against system/prebuilt
stuff in a rawhide docker image because its massively faster to do it
that way and has the advantage that the trend statistics don't include
a big unexplainable block of warnings. While I was at it I dropped the
then empty filter to keep pressure on favoring prebuilds. I've filtered
pdfium for now until the next build. It is interesting to see just how
many warnings were in there though, it is quite a large hunk of code at
280k loc.
generally we don't fix coverity warnings in code we don't maintain.
the one that bothers me the most is libxmlsec because we never got the
modifications upstream or found another way to do whatever it is we do
to it.
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.