Bug 521330

Summary: scriptlet errors during cleanup for bind-libs
Product: [Fedora] Fedora Reporter: Tom Horsley <horsley1953>
Component: bindAssignee: Adam Tkac <atkac>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: atkac, ovasik, pwouters, redhat-bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-07 08:35:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Tom Horsley 2009-09-04 20:09:33 UTC
Description of problem:
Just doing a yum update on my rawhide partition and saw this:

  Cleanup        : 32:bind-libs-9.6.1-8.P1.fc12.x86_64                  305/480 
/sbin/ldconfig: relative path `1' used to build cache
Non-fatal POSTUN scriptlet failure in rpm package bind-libs
  Cleanup        : openssh-5.2p1-21.fc12.x86_64                         306/480 
warning: %postun(bind-libs-32:9.6.1-8.P1.fc12.x86_64) scriptlet failed, exit status 1

There is no component named bind-libs to report this against, so
I guess the component that had both bind and lib in the name :-).

Version-Release number of selected component (if applicable):

How reproducible:
I only installed once, so it is hard to say.

Steps to Reproduce:
1. see above
Actual results:
funny messages

Expected results:
no messages

Additional info:

Comment 1 Robert Scheck 2009-09-04 22:53:23 UTC
When do people learn, that "bind-libbind" is NOT the same as "bind-libs"? The
"bind-libbind" package does NOT exist on anything except EPEL 4! Please use in
the future "rpm -qi bind-libs" command and have a look what the source rpm 
package name is - that's the component you can use for bugzilla.

Comment 2 Adam Tkac 2009-09-07 08:35:42 UTC

*** This bug has been marked as a duplicate of bug 520385 ***