I'm seeing these warnings on several samba packages updates: Cleanup : 2:samba-libs-4.0.0-160.fc18.rc3.x86_64 172/200 /sbin/ldconfig: relative path `1' used to build cache warning: %postun(samba-libs-2:4.0.0-160.fc18.rc3.x86_64) scriptlet failed, exit status 1 Non-fatal POSTUN scriptlet failure in rpm package 2:samba-libs-4.0.0-160.fc18.rc3.x86_64
%postun libs -p /sbin/ldconfig That's the postun scriptlet. I don't see what's wrong with it. Setting component to rpm to ask for clarification.
*** Bug 870787 has been marked as a duplicate of this bug. ***
Just a wild guess here but isn't it possible that /sbin/ldconfig is a symlink with relative path used in it?
The problem looks related to usrmove. The new location of ldconfig in F18 is actually /usr/sbin/ldconfig what also explains the scriptlet failure.
Nah, its just a silly little packaging bug. Comments in specs can end up in unexpected places - shell would not complain about it, ldconfig does not accept such input however: [pmatilai@localhost Downloads]$ rpm -qp --nosignature --scripts samba-libs-4.0.0-160.fc18.rc3.x86_64.rpm postinstall program: /sbin/ldconfig postuninstall scriptlet (using /sbin/ldconfig): ### LIBSMBCLIENT [pmatilai@localhost Downloads]$
So I can't add any comments in these sections, cause comments are not ignored?
Rpm cannot go interpreting (including ignoring comments) the scriptlet sections in any way. While # is a comment marker in some languages but not all, and even in shell its not so simple - consider eg the following: %post if [ ! -f /etc/foo.conf ]; then cat << EOF >> # This space intentionally left blank EOF The "issue" is that the spec syntax does not have section end marker, so a section ends only when a new one starts. That's the way the entire spec behaves, but its only really user-visible with the scriptlets.
I will fix it with the update tomorrow.
*** Bug 871041 has been marked as a duplicate of this bug. ***
samba-4.0.0-163.fc18.rc4 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/samba-4.0.0-163.fc18.rc4
Package samba-4.0.0-163.fc18.rc4: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing samba-4.0.0-163.fc18.rc4' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-17235/samba-4.0.0-163.fc18.rc4 then log in and leave karma (feedback).
samba-4.0.0-165.fc18.rc4 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/samba-4.0.0-165.fc18.rc4
samba-4.0.0-165.fc18.rc4 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.