Debian Bug report logs - #961954
lirc: Disable embedding of build path in documentation

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@reproducible-builds.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: lirc: Disable embedding of build path in documentation

Date: Sun, 31 May 2020 20:21:58 -0700

[Message part 1 (text/plain, inline)]

Source: lirc
Version: 0.10.1-6.2
Severity: normal
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-bugs@lists.alioth.debian.org

The build path is embedded in the generated documentation, which breaks
reproducibility when built from a different path.

The attached patch sets "FULL_PATH_NAMES = NO", which changes the
behavior to only embed the unique part of the filename.

There are other outstanding issues reproducibility issues, but applying
this patch makes it easier to identify and troubleshoot the remaining
issues.

Thanks for considering!

live well,
  vagrant

[0001-doc-Doxyfile-set-FULL_PATH_NAMES-NO-to-make-reproduc.patch (text/x-diff, inline)]

From 11911fc80b2772aa48f06cd8ab36a85bc2b52e59 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <vagrant@reproducible-builds.org>
Date: Mon, 1 Jun 2020 02:10:44 +0000
Subject: [PATCH] doc/Doxyfile: Do not embed build path in documentation.

Disable FULL_PATH_NAMES to make documentation builds reproducible.

---
 doc/Doxyfile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/Doxyfile b/doc/Doxyfile
index 1960b07..7997407 100644
--- a/doc/Doxyfile
+++ b/doc/Doxyfile
@@ -119,7 +119,7 @@ INLINE_INHERITED_MEMB  = NO
 # path before files name in the file list and in the header files. If set
 # to NO the shortest path that makes the file name unique will be used.
 
-FULL_PATH_NAMES        = YES
+FULL_PATH_NAMES        = NO
 
 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
 # can be used to strip a user-defined part of the path. Stripping is
-- 
2.20.1

[signature.asc (application/pgp-signature, inline)]

Message #10 received at 961954@bugs.debian.org (full text, mbox, reply):

From: Alec Leamas <leamas.alec@gmail.com>

To: 961954@bugs.debian.org

Subject: Re: lirc: Disable embedding of build path in documentation

Date: Tue, 27 Oct 2020 09:48:52 +0100

On Sun, 31 May 2020 20:21:58 -0700 Vagrant Cascadian
<vagrant@reproducible-builds.org> wrote:

> The build path is embedded in the generated documentation, which breaks
> reproducibility when built from a different path.


Fixed in git repo, will not make a release for this issue only.

Message #15 received at 961954@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@reproducible-builds.org>

To: Alec Leamas <leamas.alec@gmail.com>, 961954@bugs.debian.org

Subject: Re: Bug#961954: lirc: Disable embedding of build path in documentation

Date: Fri, 01 Jan 2021 15:33:20 -0800

[Message part 1 (text/plain, inline)]

Control: tags 961954 pending

On 2020-10-27, Alec Leamas wrote:
> On Sun, 31 May 2020 20:21:58 -0700 Vagrant Cascadian
> <vagrant@reproducible-builds.org> wrote:
>
>> The build path is embedded in the generated documentation, which breaks
>> reproducibility when built from a different path.
>
>
> Fixed in git repo, 

Thanks!

For the record, the commit is:

  https://gitlab.com/leamas/lirc/-/commit/834f71d34b428b5dcf1897ee824fe198c9481a6b


> will not make a release for this issue only.

Ok, I'll try to file more patches then. :)


live well,
  vagrant

p.s. please CC me or submitter-NNN@bugs.debian.org on future replies, as
NNN@bugs.debian.org does not typically get sent to the committer.

[signature.asc (application/pgp-signature, inline)]

Message #22 received at 961954-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 961954-close@bugs.debian.org

Subject: Bug#961954: fixed in lirc 0.10.1-7

Date: Thu, 12 May 2022 21:36:06 +0000

Source: lirc
Source-Version: 0.10.1-7
Done: Alec Leamas <leamas.alec@gmail.com>

We believe that the bug you reported is fixed in the latest version of
lirc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 961954@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alec Leamas <leamas.alec@gmail.com> (supplier of updated lirc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 12 May 2022 21:29:00 +0200
Source: lirc
Architecture: source
Version: 0.10.1-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Lirc Team <team+debian-lirc@tracker.debian.org>
Changed-By: Alec Leamas <leamas.alec@gmail.com>
Closes: 961954 1009389
Changes:
 lirc (0.10.1-7) unstable; urgency=medium
 .
   * Add patch from Fedora for failing tests. Closes: #1009389
   * Add patch avoiding build path in docs. Closes: #961954
Checksums-Sha1:
 63a7b49d292778ca5835cfd9d71d7d1856226849 2505 lirc_0.10.1-7.dsc
 caf0c2c39aa786017359a92225ab172f087004d3 39392 lirc_0.10.1-7.debian.tar.xz
 e09a5bf22c99c137bec6f7898e3299905cefa04c 8534 lirc_0.10.1-7_source.buildinfo
Checksums-Sha256:
 b1f09e490b8552eb56e10cd067f2b2bb6281bad29722dab93ee7c770c54d8aef 2505 lirc_0.10.1-7.dsc
 c474901a1fe8b27a435bd7b05b8017617fd1a920c06ff350248f004f93b7adff 39392 lirc_0.10.1-7.debian.tar.xz
 0216dd8dd1a31ac7357b413a035054c71cb0be2185d7ce41c9df24c52dc9f34c 8534 lirc_0.10.1-7_source.buildinfo
Files:
 826ac07721f1f7230a4a1b04a4829f57 2505 utils optional lirc_0.10.1-7.dsc
 f10f898bf3c4b97fbdf9db3cb9472622 39392 utils optional lirc_0.10.1-7.debian.tar.xz
 83452e8ac9d999ff5c6ac93a2b5e8ccd 8534 utils optional lirc_0.10.1-7_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmJ9ePgQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFKvtC/sEAiVjLu5a/AYzaahRSvkG09lqj6i50NTT
8UbtwE4m6lAiGGEmJc1RYsobBKA1o+2JfFwdV2Fcyt4lzPbUCTeFr9N9NG+c9Qdc
JTyBTcWF+FybtRTky6W4z2jt6w9vqmMx2bZRO+r246vMsQgQW88d3+dwpV4cWCmK
jfhGV6GmfQKKgAq0nUbk0seGXSJ+FdkuwWZ68iDSObiR9k5+qhoowhzrsI0WSy95
hoZVA0ReAYXsk4kSyc9Gj0QoYPhZZrRlQWPYo0bwlYhVRqcBzjSgMFwiXiWO0FhA
CrzVE9zPLvqnYlU/XpXy/qMCLxAxgyOfCkVYB+CV27MkNT8suPFOWK2I2ZauDCTa
GM+ATHsjfTQN1i7uoEJrRMXCLxvHjF+GnaqSlQu8szsxHwJ7miDx/mT8ypjTktMI
V5k12wr15hvG4dyoXjX3n49iuoR5LjcTLuBagLxHktKAR9Bkc2gwpKsgM+VIVXbk
zu5yBc70pO5QaKuDzJTfVkFovZHA11s=
=WAjO
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.