Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Default install produced errors in install.log:
Version-Release number of selected component (if applicable):
samba-common-3.6.5-88.el7.1.x86_64
How reproducible:
deterministic
Steps to Reproduce:
1. yum install samba-common -y
2.
3.
Actual results:
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
Expected results:
no warning
Additional info:
/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
Comment 5Andreas Schneider
2012-06-19 09:16:11 UTC
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:
/usr/bin/ldconfig
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
before samba?
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.