bind-libs %postun is trying to use /lib/ldconfig as a "shell". Cleanup : 32:bind-libs-9.6.1-7.P1.fc12.x86_64 149/222 /sbin/ldconfig: relative path `1' used to build cache Non-fatal POSTUN scriptlet failure in rpm package b warning: %postun(bind-libs-32:9.6.1-7.P1.fc12.x86_64) scriptlet failed, exit status 1 $ rpm -q bind-libs --scripts postinstall program: /sbin/ldconfig postuninstall scriptlet (using /sbin/ldconfig): # bind-libs between 32:9.6.1-0.1.b1 and 32:9.6.1-0.4.rc1 have bigger SOnames # than current bind - https://bugzilla.redhat.com/show_bug.cgi?id=509635. # Remove this trigger when SOnames get bigger.
*** Bug 513016 has been marked as a duplicate of this bug. ***
Chm, it seems the first attempt to fix this issue was not successful (bug #513016).
The problem is that the specfile "language" does not have the concept of comments. The body of the %postun script extends into the start of the next section (%triggerpostun in this case). Your last attempt didn't change anything after all.
Yes, it seems the specfile grammar doesn't include comments despite all docs say that comments start with '#'. I improved the postun scripplet so bind-9.6.1-9.P1.fc12 should be fine.
*** Bug 521330 has been marked as a duplicate of this bug. ***
I'm having the same problem on *Fedora 11* when upgrading from bind-libs-9.6.1-4.P1.fc11.x86_64 (to bind-libs-9.6.1-6.P1.fc11.x86_64.rpm). Should I report another bug for Fedora 11?
(In reply to comment #6) > I'm having the same problem on *Fedora 11* when upgrading from > bind-libs-9.6.1-4.P1.fc11.x86_64 (to bind-libs-9.6.1-6.P1.fc11.x86_64.rpm). > Should I report another bug for Fedora 11? No. This bug was in postun script which means it is present even when you update to fixed 9.6.1-6.P1.fc11. This bug won't be present when you update from 9.6.1-6.P1.fc11 to newer version.
(In reply to comment #7) > No. This bug was in postun script which means it is present even when you > update to fixed 9.6.1-6.P1.fc11. This bug won't be present when you update from > 9.6.1-6.P1.fc11 to newer version. Ok. I wanted to be sure that it's fixed in Fedora 11, too.