Backport: Update libtiff from 4.7.1 to 4.7.2 (19-5-stable)

What does this MR do?

Backports !10038 (merged) to 19-5-stable. It updates the bundled libtiff from 4.7.1 to 4.7.2, which includes upstream security fixes. This is a security dependency bump, so it is being backported to the supported stable branches (19-5, 19-4 and 19-3).

The commit is cherry-picked unchanged from master (5190ff7c → 4b7891fdf16 here):

  • config/software/libtiff.rb: libtiff 4.7.2 is built from the official release tarball (https://download.osgeo.org/libtiff/tiff-4.7.2.tar.gz, sha256 672bd7d10aee4606171afb864f3570b83340f6a33e2c186dc0512f7145ffdf6a) instead of the git tag. libtiff 4.7.2 needs Autoconf 2.71 or newer to bootstrap from git, which AlmaLinux 8/9, Debian 11 and openSUSE 15.6 builder images don't have; the tarball ships a pre-generated configure.
  • Removed config/patches/libtiff/remove-config-guess-sub-download.patch and config/patches/libtiff/add-libtoolize-call-to-autogen.patch, which only modified autogen.sh (no longer run).
  • Added scripts/renovate/checksums/software/libtiff.sh for future checksum updates.
  • The UBT block is unchanged apart from using default_version.

On !10038 (merged), build-package-on-all-os passed on all OSs, and the libtiff test plan passed on Debian 11 (amd64 and arm64).

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 marked as ready (not a draft) and a reviewer is requested.

For GitLab team members

  • The manual Trigger:ee-package jobs have a green pipeline running against latest commit.
  • If config/software or config/patches directories are changed, make sure the build-package-on-all-os job within the Trigger:ee-package downstream pipeline succeeded.
  • If you are changing anything SSL related, then the Trigger:package:fips manual job within the Trigger:ee-package downstream pipeline must succeed.
  • If CI configuration is changed, the branch must be pushed to dev.gitlab.org to 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.

🤖 Generated with Claude Code

Edited by Stefan Constantin

Merge request reports

Loading
Loading