Package: exiv2 / 0.28.5+dfsg-1
Metadata
Package | Version | Patches format |
---|---|---|
exiv2 | 0.28.5+dfsg-1 | 3.0 (quilt) |
Patch series
view the series filePatch | File delta | Description |
---|---|---|
non free.diff | (download) |
tests/bugfixes/github/test_pr_2000.py |
220 0 + 220 - 0 ! |
remove references to non-free excluded content |
pkgconfig no private.diff | (download) |
cmake/exiv2.pc.in |
2 0 + 2 - 0 ! |
remove private/static markers from the pkg-config file The pkg-config file lists as as private the internal libraries used by exiv2. The problem is that those private markers require the availability of those other pkg-config files to make exiv2.pc usable; since those are needed only for static linking, and that there are no static libraries, simply delete them to make exiv2.pc usable again. . This was forwarded upstream in a cleaner way together with the changes in the CMake config files, and the changes affecting the pkg-config file were rejected: https://github.com/Exiv2/exiv2/pull/2872 |
tests overflow skip unsigned char 23bit.diff | (download) |
tests/bugfixes/github/test_CVE_2018_12265.py |
6 4 + 2 - 0 ! |
tweak additionoverflowinloaderexifjpeg for 32bit unsigned char oses AdditionOverflowInLoaderExifJpeg expects an overflow to happen on 32bit architectures; due to the way LoaderExifJpeg & StringValueBase work and the test data is fabricated, the overflow happens only architectures with signed char. . Tweak AdditionOverflowInLoaderExifJpeg to account for this, by not expecting an overflow in case the architecture has unsigned char (e.g. ARM and POWER). . For more discussion and notes, see: https://github.com/Exiv2/exiv2/issues/933 |
1