Bug 90697 - post scriplet fails
Summary: post scriplet fails
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: librsvg2
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-05-12 16:30 UTC by Sepp Rudel
Modified: 2007-04-18 16:53 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2004-06-23 19:35:44 UTC


Attachments (Terms of Use)

Description Sepp Rudel 2003-05-12 16:30:08 UTC
Description of problem:
While I was updating from RHL7.3->RHL9 with apt (yea, I know, not supported by
RH, but read on...), librsvg2 gave following error:

  57:librsvg2               ########################################### [  8%]
Cannot load loader /usr/lib/gtk-2.0/2.2.0/loaders/libpixbufloader-png.so

Probably caused by the fact that also RPM containing
/usr/lib/gtk-2.0/2.2.0/loaders/libpixbufloader-png.so was about to be
updated after librsvg2 during the same "rpm -Uvh" run. This might well happen
also with up2date/rpm -Fvh/yum/etc.


Version-Release number of selected component (if applicable):
All, I presume.

How reproducible:
Always.

Steps to Reproduce:
1.update librsvg2 and RPMs containing
/usr/lib/gtk-2.0/2.2.0/loaders/libpixbufloader-png.so in the same run
    
Actual results:
error messages printed.


Expected results:
no error messages printed.


Additional info:
Probably not critical but worth fixing IMHO.

Comment 1 Sepp Rudel 2003-05-13 11:36:14 UTC
D'oh! Wrong component, now changed. librsvg2 is the problematic case.

Comment 2 Alexander Larsson 2003-05-16 12:40:43 UTC
Hmm. Interesting. It probably needs some sort of PreReq.

Comment 3 Joseph Tate 2003-11-21 07:07:16 UTC
Still exists in Fedora Core 1

Comment 4 Joseph Tate 2003-11-21 07:07:55 UTC
Doh, disregard that.  I'm seeing something else.

Comment 5 Matthias Clasen 2004-06-23 19:35:44 UTC
I've changed Requires: gtk2 to PreReq: gtk2 which should fix it.


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