Bump exiftool to 13.59

What does this MR do?

Bumps exiftool from 13.44 to 13.59, the latest upstream release (2026-05-27), and rebases allow-only-tiff-jpeg-exif-strip.patch onto it.

13.59 is also the version nixpkgs ships. The nix images need exiftool for workhorse EXIF stripping (gitlab-org/software-supply-chain-security/hardened-builds#25 (closed)), and the agreed approach there is the nixpkgs version plus this patch, not a pin to an older release (gitlab-org/software-supply-chain-security/hardened-builds!251 (comment 4083759245)). Bumping CNG first keeps the Debian, UBI and nix images on the same exiftool with the same patch.

The patch

The 13.44 patch no longer applies: 13.59 added types to @fileTypes (FIT) and entries to %fileTypeLookup, so both lib/Image/ExifTool.pm hunks conflict, and lib/Image/ExifTool/AIFF.pm changed. I rebased it with a 3-way merge (13.44 → 13.44 patched, replayed onto 13.59, taking the patch side only in the conflicting hunks). The result does exactly what it did before:

  • @fileTypes and @writeTypes are qw(JPEG TIFF).
  • %fileTypeLookup is byte-identical to the 13.44 patched one (JPEG, JPG, TIFF).
  • lib/Image/ExifTool/AIFF.pm is deleted.
  • Everything else in ExifTool.pm is 13.59 ($VERSION = '13.59'), and perl -c passes.

Test plan

Locally, with the 13.59 tarball from https://gitlab.com/gitlab-org/build/omnibus-mirror/exiftool and the new patch, using workhorse's arguments (-all= -tagsFromFile @ <allowlisted tags> -) on stdin:

Input Patched 13.59 Unpatched 13.59
t/images/GPS.jpg (5 GPS tags) exit 0, valid JPEG, 0 GPS tags exit 0, 0 GPS tags
t/images/PNG.png exit 1, Unknown file type exit 0, processed
  • gitlab-exiftool builds on Debian and UBI in the pipeline.
  • Workhorse QA upload specs pass.

Omnibus GitLab is also on 13.44 with its own allowlist-types.patch (its Renovate bumps, e.g. gitlab-org/omnibus-gitlab!9861, were abandoned). The last CNG bump aligned with Omnibus; a matching Omnibus bump should follow.

Checklist

See Definition of done.

Required

  • Merge Request Title, and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com
  • When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated: not needed
  • Integration tests added to GitLab QA: existing upload specs cover it
  • The impact any change in container size has should be evaluated: negligible, same patch scope
  • New dependencies are managed with GitLab forked renovatebot: no new dependency

🤖 Generated with Claude Code

Edited by Robert Marshall

Merge request reports

Loading
Loading