Red Hat Bugzilla – Bug 835952
doxygen generated pdf files are different in x86 and x86_64 builds
Last modified: 2015-02-17 09:19:00 EST
Description of problem:
doxygen generated pdf files are different in x86 and x86_64 builds because of the front page and footer include the creation date. This is causing an rpm file conflict when said pdf file is present at the same location for rpms of different architecture.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. build libbluray. It uses doxygen to generate a pdf file that is included at the same location in both the 32 and 64 bits builds.
2. try to install both libbluray-devel-0.2.2-2.fc18.x86_64.rpm and libbluray-devel-0.2.2-2.fc18.i686.rpm
Generated pdf file is different in the x86 and x86_64 build, causing an rpm file conflict.
Generated pdf files are identical, both the x86 and x86_64 rpms can be installed at the same time.
libbluray build with the conflicting pdf files :
start of the fedora-devel thread where the issue is discussed :
mail where the bug is detailed :
to help so no one has to go searching onlist,
> This build has the pdf file with a different timestamp in the i686 and
> x86_64 build.
> The pdf file is /usr/share/doc/libbluray-devel-0.2.2/libbluray.pdf from
it's a bug in pdftex (part of texlive package) which is used to create pdf
files. pdftex writes the timestamps "CreationDate (%s)" and "ModDate (%s)"
into PDF files.
extract from texk/web2c/pdftexdir/utils.c
pdf_printf("/CreationDate (%s)\n", start_time_str);
pdf_printf("/ModDate (%s)\n", start_time_str);
It seems more like doxygen bug to me. There is a hyperref package which allows to influence pdf metadata:
Not sure if it is a good idea to omit these fields globally to workaround pdflatex's default behaviour.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.