Your message dated Wed, 04 Oct 2023 09:09:27 +0200
with message-id <[email protected]>
and subject line these were fixed in the package
has caused the Debian Bug report #1015246,
regarding zeal: please make the build reproducible
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1015246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015246
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: zeal
Version: 1:0.6.1+git20220714+6fee23-1
Severity: wishlist
Tags: patch
User: [email protected]
Usertags: timestamps
X-Debbugs-Cc: [email protected]
Hi,
Whilst working on the Reproducible Builds effort [0] we noticed that
zeal could not be built reproducibly.
This is because it adds a "development release" date to an XML file:
│ │ │ │ ├── ./usr/share/metainfo/org.zealdocs.zeal.appdata.xml
│ │ │ │ │ @@ -23,15 +23,15 @@
│ │ │ │ │ <image>https://i.imgur.com/qBkZduS.png</image>
│ │ │ │ │ </screenshot>
│ │ │ │ │ </screenshots>
│ │ │ │ │ <provides>
│ │ │ │ │ <id>zeal.desktop</id>
│ │ │ │ │ </provides>
│ │ │ │ │ <releases>
│ │ │ │ │ - <release date="2022-07-15" version="0.6.2-dev"
type="development"/>
│ │ │ │ │ + <release date="2022-07-16" version="0.6.2-dev"
type="development"/>
Patch attached that simply drops this line.
[0] https://reproducible-builds.org/
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` [email protected] / chris-lamb.co.uk
`-
--- a/debian/patches/reproducible-build.patch 1970-01-01 01:00:00.000000000
+0100
--- b/debian/patches/reproducible-build.patch 2022-07-18 11:47:48.221289879
+0100
@@ -0,0 +1,18 @@
+Description: Make the build reproducible
+Author: Chris Lamb <[email protected]>
+Last-Update: 2022-07-18
+
+--- zeal-0.6.1+git20220714+6fee23.orig/CMakeLists.txt
++++ zeal-0.6.1+git20220714+6fee23/CMakeLists.txt
+@@ -44,11 +44,6 @@ endif()
+
+ set(ZEAL_VERSION_FULL "${Zeal_VERSION}${ZEAL_VERSION_SUFFIX}")
+
+-# For development builds insert an extra release in the AppStream metadata.
+-if(NOT RELEASE_VERSION)
+- string(TIMESTAMP ZEAL_APPSTREAM_DEV_RELEASE "\n <release
date=\"%Y-%m-%d\" version=\"${ZEAL_VERSION_FULL}\" type=\"development\" />")
+-endif()
+-
+ # A custom target to print the full version.
+ # Usage: cmake --build build --target zeal_version
+ add_custom_target(zeal_version
--- a/debian/patches/series 2022-07-18 11:36:13.167186089 +0100
--- b/debian/patches/series 2022-07-18 11:47:47.389286997 +0100
@@ -1,2 +1,3 @@
disable-check-for-update.patch
#system-cpp-httplib.patch # only needed with the next upstream release
+reproducible-build.patch
--- End Message ---
--- Begin Message ---
Version: 1:0.7.0-2
Hello,
these two bugs were fixed in the 1:0.7.0-2 version of the Zeal package, but I
had a typo in the changelog. I wrote "close:" instead of the expected "closes:"
Sorry for that, and thanks for the fish
Mt
signature.asc
Description: This is a digitally signed message part
--- End Message ---
