Bug 1264116 - gtkdoc-mkpdf doesn't have references to dblatex nor fop
gtkdoc-mkpdf doesn't have references to dblatex nor fop
Status: CLOSED EOL
Product: Fedora
Classification: Fedora
Component: gtk-doc (Show other bugs)
22
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Matthias Clasen
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-17 10:25 EDT by Pierre
Modified: 2016-07-19 15:57 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-19 15:57:03 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Pierre 2015-09-17 10:25:46 EDT
Description of problem:
gtkdoc-mkpdf fails to build pdf documents with message
"dblatex or fop must be installed to use gtkdoc-mkpdf."

Version-Release number of selected component (if applicable):
gtk-doc-1.24-1.fc22.noarch

How reproducible:
Always

Steps to Reproduce:
1. Have a product which is willing to generate some gtk-doc-enabled documentation (e.g. nautilus-actions in my case)
2. Configure it with --enable-gtk-doc-pdf option.
3. make

Actual results:
"dblatex or fop must be installed to use gtkdoc-mkpdf."

Expected results:
DF documents are built with dblatex.

Additional info:
It appears that gtkdoc-mkpdf script is built when generating the package from gtkdoc-mkpdf.in, and so embeds @DBLATEX@ or @FOP@ from build system, instead of those of the running system.
Which appears to me to be bad.
Comment 1 Fedora End Of Life 2016-07-19 15:57:03 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.