Bug 175722 - Remove ldconfig, install-info commands from gimp-print-cups %post(un) and %preun scriptlets
Summary: Remove ldconfig, install-info commands from gimp-print-cups %post(un) and %pr...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gimp-print
Version: 4.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Tim Waugh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-12-14 10:31 UTC by Robert van den Aker
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-12-15 17:04:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Robert van den Aker 2005-12-14 10:31:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

Description of problem:
The %post, %preun and %postun scriplets for gimp-print-cups contain ldconfig and install-info commands which I believe are inappropriate for that sub-package. The install-info commands try to install and remove an info file that is owned by the gimp-print package, not the gimp-print-cups package. Also, the gimp-print-cups package doesn't appear to contain any shared libraries, so I don't think ldconfig needs to be run.

Version-Release number of selected component (if applicable):
gimp-print-4.2.7-2

How reproducible:
Always

Steps to Reproduce:
1. Install or uninstall gimp-print-cups
2. Receive error about non-existent info file
3.
  

Additional info:

I'm setting severity to enhancement for this bug because it doesn't affect functionality.

Comment 1 Tim Waugh 2005-12-15 17:01:16 UTC
Thanks for the report.  I have fixed this in the devel branch (for Fedora Core /
rawhide), as well as making some other small fixes in those scriptlets.

Comment 2 Tim Waugh 2005-12-15 17:04:26 UTC
Since this issue has very low impact there will not be an update package for it.


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