Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 159676 - ImageMagick install/update fails -- libgs dependency
Summary: ImageMagick install/update fails -- libgs dependency
Alias: None
Product: Fedora
Classification: Fedora
Component: ImageMagick
Version: 4
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2005-06-06 21:27 UTC by Jonathan S. Shapiro
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-09-30 23:20:01 UTC
Type: ---

Attachments (Terms of Use)

Description Jonathan S. Shapiro 2005-06-06 21:27:37 UTC
ImageMagic.i386 version fails to install/upgrade because it relies on
libgs.so.7, which has been supersceded in ghostscript version 8 by libgs.so.8.
This means that the current development tree doesn't update cleanly.

This is high priority because ghostscript and ImageMagick are likely to be
installed simultaneously in ordinary installs of FC4, and the install will fail
in this case because of RPM dependency conflicts.

This class of bug has happened multiple times in the FC4test cycles. I want to
suggest that a new step needs to be integrated into the RPM update push cycle,
and I'm not sure where to file that RFE. The test is that there should be a
machine somewhere that has *everything* installed, and before the internal
bundle of updates is pushed somebody should run a "yum update" on that machine
to check for upgrade conflicts. We've had a couple of cases where updates were
stalled for several days by this class of error (last time it was the OpenOffice
build), and it's completely unnecessary.

Comment 1 Matthias Clasen 2005-09-30 23:20:01 UTC
Hmm, I still see ghostscript 7 in FC4. ghostscript 8 is in Rawhide, but there
the problem is fixed since ImageMagick has been rebuilt against it.

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