Source: kvirc
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: username
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The username is embedded in various .html documentation files:

  
https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/kvirc.html

  ./usr/share/kvirc/5.0/help/en/class_button.html

  
<div·class='footer'>KVIrc·5.0.0·Documentation·-·generated·by·pbuilder1·on·Sat·Jul·10·07:26:08·2021</div>
vs.
  
<div·class='footer'>KVIrc·5.0.0·Documentation·-·generated·by·pbuilder2·on·Sat·Jul·10·07:26:08·2021</div>

The attached patch fixes this by removing the username from gendoc.pl
which generates the documentation.

The patch also removes the timestamp, which appears to respect
SOURCE_DATE_EPOCH and is reproducible, but does not really convey useful
information for the documentation.


With these patches applied, kvirc should become reproducible on
tests.reproducible-builds.org when the patched version lands in
bookworm/testing (there are build path variations tested for
experimental/unstable that are unresolved).


Thanks for maintaining kvirc!


live well,
  vagrant
From 49843daa21cd2df04694340eca7ff2059dcab372 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <vagr...@reproducible-builds.org>
Date: Fri, 22 Oct 2021 17:57:50 +0000
Subject: [PATCH 2/2] admin/gendoc.pl: Remove user and timestamp from generated
 documentation.

---
 admin/gendoc.pl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/admin/gendoc.pl b/admin/gendoc.pl
index 6ee0959..2576da1 100755
--- a/admin/gendoc.pl
+++ b/admin/gendoc.pl
@@ -203,7 +203,7 @@ sub print_header
 
 sub print_footer
 {
-	print $g_filehandle "<div class='footer'>KVIrc $g_version Documentation - generated by $g_currentuser on $g_currenttime</div>\n";
+	print $g_filehandle "<div class='footer'>KVIrc $g_version Documentation</div>\n";
 	print $g_filehandle "</body>\n";
 	print $g_filehandle "</html>\n";
 }
-- 
2.33.0

Attachment: signature.asc
Description: PGP signature

Reply via email to