Hi Enrico, > Yes, because it knows where to find it and that it is gzipped. I don't > mind moving it to /usr/share, for example, and shipping it non > gzipped.
I have no input on this. It's unrelated to unreproducibility after all; I only mentioned the location and it being gzipped because I was (incorrectly, according to your clarifications) inferring that it meant that the file was not being consumed mechanically. > That sounds like a very good thing to do. I had not realised that > doxygen tags files contained absolute paths. I consider that to be a > potential leak of private data, on top of being a reproducibility issue. Indeed. Reproducibility is great for finding QA issues as well as security ones (see, for example <https://bugs.debian.org/833885>). Anyway, here is an alternative patch: --- a/debian/rules 2018-02-14 22:40:51.055273779 +0000 --- b/debian/rules 2018-02-15 14:41:23.016460856 +0000 @@ -26,6 +26,9 @@ done # Remove python modules .la files rm -f debian/tmp/usr/lib/python*/dist-packages/*.la + # Remove absolute build path from tag file, resulting in <path>.</path> + sed -i -e 's@$(CURDIR)@/usr/include@g' \ + debian/tmp/usr/share/doc/wreport/libwreport.doxytags vercheck: debian/vercheck > /dev/null Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
