Description of problem:
Default install produced errors in install.log:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. yum install samba-common -y
08:07:21 Installing samba-common-3.6.5-88.el7.1.x86_64
/var/tmp/rpm-tmp.OBXLMV: line 2: /bin/systemd-tmpfiles: No such file or directory
warning: %post(samba-common-2:3.6.5-88.el7.1.x86_64) scriptlet failed, exit status 127
/bin is supposed to be symlink to /usr/bin so not sure how or why this would happen
In particular, I'm not sure it is wise to use /usr/sbin/ldconfig in scriptlets, this is busted on rawhide causing builds to fail:
DEBUG util.py:257: Error: Package: 2:libsmbclient-3.6.5-89.fc18.1.x86_64 (build)
DEBUG util.py:257: Requires: /usr/sbin/ldconfig
Well then this needs to be fixed and documented in rawhide.
Why do we do the usrmove if /usr/sbin/ldconfig is wrong? I don't think this is a Samba bug then.
Packaging guidelines (still) say to use, /sbin/ldconfig. I'd recommend you continue to do so. I'd recommend doing the same for systemd too, fwiw.
The issue as reported in comment #1 is indeed not samba's fault or bug. It's some usrmove (or systemd) failure.
glibc.rpm has not moved to /usr so far, so nothing explicitly provides:
for RPM, and therefore there can not be a Requires: (RPM adds that if you use
that path) inside a transaction that has it not already installed, even when
the binary will finally end up there.
Either glibc would need to move to /usr, or it will need an explicit
Provides: /usr/bin/ldconfig to make things like the samba spec file work.
There is no real need to convert these paths to the /usr locations.
The error in comment#0 is during install when systemd is not installed
I doubt it can be fixed with changing the called paths, they are both
valid if the tool is there.
Not sure, but it might rather need a "Requires(post): systemd" to enforce
proper install ordering.
Note that this issue has broken things for me. Both building live images using f17 updates-testing and doing an update of glibc from f17 updates-testing were broken.
*** Bug 834209 has been marked as a duplicate of this bug. ***
the not for UsrMove prepared bash-package is the root cause of these problems