Hi,
On 02/16/2015 02:43 PM, marivalen wrote:
Hi,
[...]
Furthermore the Doxyfile configuration file embedded in each package
using doxygen is often copied from the upstream defaults and thus
enables HTML_TIMESTAMP. The following query on codesearch.d.n shows that
277 source packages are affected:
http://codesearch.debian.net/results/HTML_TIMESTAMP%20%2B%3D%20YES%20path%3ADoxyfile/page_0
So no matter whether my patch to doxygen is applied or not, these 277
source packages will either need individual fixes or a change to doxygen
which allows to ignore the setting of HTML_TIMESTAMP in Doxyfile. I can
implement this but this again has to be discussed with the Debian
maintainers and doxygen upstream.
I made an error in my earlier analysis. The 277 packages found by
codesearch.d.n are not 277 out of the 297 packages that are tagged with
timestamps_in_documentation_generated_by_doxygen. In fact 154 of these
277 source packages that contain HTML_TIMESTAMP = YES are actually
marked as being reproducible by jenkins. Only 83 of the 277 packages
intersect with the 297 packages which are tagged with
timestamps_in_documentation_generated_by_doxygen.
70% of the 297 packages tagged with
timestamps_in_documentation_generated_by_doxygen do not contain the
string HMTL_TIMESTAMP at all thus they should be influenced by the
default value for HTML_TIMESTAMP set in doxygen.
I uploaded a version of doxygen to the experimental reproducible builds
toolchain repository which changes the default value of HTML_TIMESTAMP
from YES to NO. Could you please reschedule the following 343 packages
which build-depend on doxygen and fail to build reproducibly:
https://mister-muffin.de/p/2NL4.txt
I also made a bug report to upstream about changing the default (see
https://bugzilla.gnome.org/show_bug.cgi?id=745439 ).
Cheers, akira
_______________________________________________
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
