Bug#968627: #968627: libjpeg-turbo: Use UTC timestamp for build date

[Vagrant Cascadian]

On 2020-08-18, Vagrant Cascadian wrote:
> From 9a7f5e988f982f0e957eb08ad9122388ba376569 Mon Sep 17 00:00:00 2001
> From: Vagrant Cascadian <vagr...@reproducible-builds.org>
> Date: Tue, 18 Aug 2020 18:47:02 +0000
> Subject: [PATCH] Add patch to use UTC timestamp to enable reproducible build.
>
> ---
>  debian/patches/1001-use-utc-timestamp.patch | 21 +++++++++++++++++++++
>  debian/patches/series                       |  1 +
>  2 files changed, 22 insertions(+)
>  create mode 100644 debian/patches/1001-use-utc-timestamp.patch
>
> diff --git a/debian/patches/1001-use-utc-timestamp.patch 
> b/debian/patches/1001-use-utc-timestamp.patch
> new file mode 100644
> index 0000000..e689e4d
> --- /dev/null
> +++ b/debian/patches/1001-use-utc-timestamp.patch
> @@ -0,0 +1,21 @@
> +Author: Vagrant Cascadian <vagr...@reproducible-builds.org>
> +Description: Use UTC timezone for build timestamp
> +
> +While CMake respects SOURCE_DATE_EPOCH, it still can produce a
> +different date depending on the timezone of the running system.
> +
> +Specify timezone in UTC to enable a reproducible build.
> +
> +Index: libjpeg-turbo/CMakeLists.txt
> +===================================================================
> +--- libjpeg-turbo.orig/CMakeLists.txt
> ++++ libjpeg-turbo/CMakeLists.txt
> +@@ -25,7 +25,7 @@ pad_number(VERSION_MINOR 3)
> + pad_number(VERSION_REVISION 3)
> + set(LIBJPEG_TURBO_VERSION_NUMBER 
> ${VERSION_MAJOR}${VERSION_MINOR}${VERSION_REVISION})
> + 
> +-string(TIMESTAMP DEFAULT_BUILD "%Y%m%d")
> ++string(TIMESTAMP DEFAULT_BUILD "%Y%m%d" UTC)
> + set(BUILD ${DEFAULT_BUILD} CACHE STRING "Build string (default: 
> ${DEFAULT_BUILD})")
> + 
> + # NOTE: On Windows, this does nothing except when using MinGW or Cygwin.
> diff --git a/debian/patches/series b/debian/patches/series
> index 281f1c6..c226907 100644
> --- a/debian/patches/series
> +++ b/debian/patches/series
> @@ -1 +1,2 @@
> +1001-use-utc-timestamp.patch
>  2001_dont-set-RPATH.patch
> -- 
> 2.28.0

Any chance we can see this applied in time for bullseye?

The maintainer field indicates https://wiki.debian.org/LowThresholdNmu
so I guess I'll proceed with an NMU unless I hear otherwise soon.


live well,
  vagrant

signature.asc
Description: PGP signature