Your message dated Fri, 21 Aug 2015 17:03:23 +0200 with message-id <55D73DBB.1010004@gmail.com> and subject line Please close bug report has caused the Debian Bug report #789071, regarding libxkbcommon: 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 owner@bugs.debian.org immediately.) -- 789071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789071 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: libxkbcommon: please make the build reproducible
- From: Maria Valentina Marin <marivalenm@gmail.com>
- Date: Wed, 17 Jun 2015 16:46:38 +0200
- Message-id: <20150617144638.31228.50971.reportbug@fenix>
Source: libxkbcommon Version: 0.5.0-1 Severity: wishlist Tags: patch User: reproducible-builds@lists.alioth.debian.org Usertags: timestamps Hi, While working on the “reproducible builds” effort [1], we have noticed that libxkbcommon could not be built reproducibly. The attached patch changes the value of HTML_TIMESTAMP in upstream's doxyfile to NO. Once applied libxkbcommon can be built reproducibly in our current experimental framework. Patching upstream doxyfile is necessary in this case because of the following reasons: 1. Even though the doxygen upstream changed the default value of HTML_TIMESTAMP from YES to NO this does not affect this package because the value of HTML_TIMESTAMP is explicitly set to YES. 2. Upstream's doxyfiles cannot reliably be modified to change the value of HTML_TIMESTAMP during the build process because dh_doxygen is only run after the build already completed and even adding a new dh command cannot solve the problem because there exists no sane and reliable solution to detect the file which will be used as the configuration file for doxygen (it is not always called doxyfile). 3. In case of this source package a patch against upstream is necessary in contrast to a patch against Debian rules because this source package does not call doxygen in debian/rules. Please also consider forwarding this patch upstream. Cheers! akira [1]: https://wiki.debian.org/ReproducibleBuildsdiff -u libxkbcommon-0.5.0/debian/changelog libxkbcommon-0.5.0/debian/changelog --- libxkbcommon-0.5.0/debian/changelog +++ libxkbcommon-0.5.0/debian/changelog @@ -1,3 +1,10 @@ +libxkbcommon (0.5.0-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Set HTML_TIMESTAMP from YES to NO to make package reproducible + + -- akira <marivalenm@gmail.com> Wed, 17 Jun 2015 14:52:20 +0200 + libxkbcommon (0.5.0-1) unstable; urgency=medium * New upstream release. only in patch2: unchanged: --- libxkbcommon-0.5.0.orig/doc/Doxyfile.in +++ libxkbcommon-0.5.0/doc/Doxyfile.in @@ -965,7 +965,7 @@ # page will contain the date and time when the page was generated. Setting # this to NO can help when comparing the output of multiple runs. -HTML_TIMESTAMP = YES +HTML_TIMESTAMP = NO # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML # documentation will contain sections that can be hidden and shown after the
--- End Message ---
--- Begin Message ---
- To: 789071-done@bugs.debian.org
- Subject: Please close bug report
- From: Maria Valentina Marin <marivalenm@gmail.com>
- Date: Fri, 21 Aug 2015 17:03:23 +0200
- Message-id: <55D73DBB.1010004@gmail.com>
Hi, This issue has been fixed through another way. Therefore my report should be closed. Kind Regards, akiraAttachment: signature.asc
Description: OpenPGP digital signature
--- End Message ---