Bump exiftool to 13.59
What does this MR do?
Bumps exiftool from 13.44 to 13.59 (latest upstream release, 2026-05-27), matching the version already shipped by CNG in gitlab-org/build/CNG!3217 (merged). This keeps the Debian, UBI, nix, and Omnibus packages on the same exiftool version with the same patch.
Changes:
config/software/exiftool.rb: bump the pinned version from13.44to13.59.config/patches/exiftool/allowlist-types.patch: rebase the allowlist patch for 13.59 (13.59 addedFITto@fileTypes, new%fileTypeLookupentries, and changedlib/Image/ExifTool/AIFF.pm), reusing the equivalent patch already rebased by CNG (allow-only-tiff-jpeg-exif-strip.patch). Patch behavior is unchanged:@fileTypesand@writeTypesareqw(JPEG TIFF)%fileTypeLookuponly containsJPEG,JPG,TIFFlib/Image/ExifTool/AIFF.pmis deleted
The 13.59 source is already available in the mirror: https://gitlab.com/gitlab-org/build/omnibus-mirror/exiftool
Signed-off-by: psingh29 <psingh@gitlab.com>
Related issues
Closes #10184 (closed)
Test plan
Using workhorse's arguments (-all= -tagsFromFile @ <allowlisted tags> -) on stdin:
| Input | Patched 13.59 expected |
|---|---|
t/images/GPS.jpg (5 GPS tags) |
exit 0, valid JPEG, 0 GPS tags |
t/images/PNG.png |
exit 1, Unknown file type |
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion.
Required
- MR title and description are up to date, accurate, and descriptive.
- MR targeting the appropriate branch.
- Latest Merge Result pipeline is green.
- When ready for review, MR is labeled workflowready for review per the Distribution MR workflow.
For GitLab team members
If you don't have access to this, the reviewer should trigger these jobs for you during the review process.
- The manual
Trigger:ee-packagejobs have a green pipeline running against latest commit. - If
config/softwareorconfig/patchesdirectories are changed, make sure thebuild-package-on-all-osjob within theTrigger:ee-packagedownstream pipeline succeeded. - If you are changing anything SSL related, then the
Trigger:package:fipsmanual job within theTrigger:ee-packagedownstream pipeline must succeed. - If CI configuration is changed, the branch must be pushed to
dev.gitlab.orgto confirm regular branch builds aren't broken.
Expected (please provide an explanation if not completing)
- Test plan indicating conditions for success has been posted and passes.
- Documentation created/updated.
- Tests added.
- Integration tests added to GitLab QA.
- Equivalent MR/issue for the GitLab Chart opened.
- Validate potential values for new configuration settings. Formats such as integer
10, duration10s, URIscheme[REDACTED]host:portmay require quotation or other special handling when rendered in a template and written to a configuration file.