RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 849985 - perl version/invocation failure during publican run
Summary: perl version/invocation failure during publican run
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ImageMagick
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Benjamin Tissoires
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-21 12:23 UTC by Frank Ch. Eigler
Modified: 2014-02-19 14:04 UTC (History)
1 user (show)

Fixed In Version: ImageMagick-6.7.8.9-9.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-19 14:04:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Frank Ch. Eigler 2012-08-21 12:23:43 UTC
During a systemtap documentation build via publican, the following is seen:

touch stamp-mandocs
make[3]: Leaving directory `/builddir/build/BUILD/systemtap-2.0/doc/SystemTap_Tapset_Reference'
Making all in beginners
make[3]: Entering directory `/builddir/build/BUILD/systemtap-2.0/doc/beginners'
publican build --formats=pdf,html --langs=en-US && \
mv build/en-US/pdf/*SystemTap_Beginners_Guide*.pdf SystemTap_Beginners_Guide.pdf
Perl API version v5.14.0 of Image::Magick does not match v5.16.0 at /usr/lib64/perl5/DynaLoader.pm line 213, <DATA> line 1662.
Compilation failed in require at /usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 11, <DATA> line 1662.
BEGIN failed--compilation aborted at /usr/share/perl5/vendor_perl/Publican/XmlClean.pm line 11, <DATA> line 1662.
Compilation failed in require at /usr/share/perl5/vendor_perl/Publican/Builder.pm line 10, <DATA> line 1662.
BEGIN failed--compilation aborted at /usr/share/perl5/vendor_perl/Publican/Builder.pm line 10, <DATA> line 1662.
Compilation failed in require at /usr/share/perl5/vendor_perl/Publican/CreateBook.pm line 13, <DATA> line 1662.
BEGIN failed--compilation aborted at /usr/share/perl5/vendor_perl/Publican/CreateBook.pm line 13, <DATA> line 1662.
Compilation failed in require at /usr/bin/publican line 17, <DATA> line 1662.
BEGIN failed--compilation aborted at /usr/bin/publican line 17, <DATA> line 1662.
&Image::Magick::constant not defined. The required ImageMagick libraries are not installed or not installed properly.
END failed--call queue aborted at /usr/bin/publican line 17, <DATA> line 1662.
make[3]: *** [SystemTap_Beginners_Guide.pdf] Error 22

Comment 4 Benjamin Tissoires 2014-02-19 14:04:19 UTC
The bug was open during early stages of RHEL 7, and we are not able to reproduce it anymore.


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