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:
After upgrading to libwbclient-4.18.3-100.el9.x86_64, I have this invalid symlink:
bash-5.1$ ls -l /etc/alternatives/libwbclient.so.0.15-64
lrwxrwxrwx 1 root root 45 Jun 22 2022 /etc/alternatives/libwbclient.so.0.15-64 -> /usr/lib64/samba/wbclient/libwbclient.so.0.15
bash-5.1$ wc /etc/alternatives/libwbclient.so.0.15-64
wc: /etc/alternatives/libwbclient.so.0.15-64: No such file or directory
Version-Release number of selected component (if applicable):
libwbclient-4.18.3-100.el9.x86_64
How reproducible:
Always
Steps to Reproduce:
1. rpm -Uvh libwbclient-4.18.3-100.el9.x86_64.rpm
2. wc /etc/alternatives/libwbclient.so.0.15-64
3.
Actual results:
wc: /etc/alternatives/libwbclient.so.0.15-64: No such file or directory
Expected results:
File does not exist
Additional info:
I think the preuninstall scriptlet is broken. It says:
bash-5.1$ rpm --scripts -q libwbclient
preuninstall scriptlet (using /bin/sh):
if [ $1 -eq 0 ]; then
/usr/sbin/update-alternatives \
--remove \
libwbclient.so.0.16-64 \
/usr/lib64/samba/wbclient/libwbclient.so.0.16
fi
/sbin/ldconfig
posttrans scriptlet (using /bin/sh):
# It has to be posttrans here to make sure all files of a previous version
# without alternatives support are removed
/usr/sbin/update-alternatives \
--install \
/usr/lib64/libwbclient.so.0.16 \
libwbclient.so.0.16-64 \
/usr/lib64/samba/wbclient/libwbclient.so.0.16 \
10
I believe the [ $1 -eq 0 ] test means that the alternative is removed
only on uninstall, so an upgrade to a new version leaves the dangling
symlink behind.
Regards,
Andy
Comment 1Andreas Schneider
2023-07-25 11:56:04 UTC
*** This bug has been marked as a duplicate of bug 2216712 ***
Description of problem: After upgrading to libwbclient-4.18.3-100.el9.x86_64, I have this invalid symlink: bash-5.1$ ls -l /etc/alternatives/libwbclient.so.0.15-64 lrwxrwxrwx 1 root root 45 Jun 22 2022 /etc/alternatives/libwbclient.so.0.15-64 -> /usr/lib64/samba/wbclient/libwbclient.so.0.15 bash-5.1$ wc /etc/alternatives/libwbclient.so.0.15-64 wc: /etc/alternatives/libwbclient.so.0.15-64: No such file or directory Version-Release number of selected component (if applicable): libwbclient-4.18.3-100.el9.x86_64 How reproducible: Always Steps to Reproduce: 1. rpm -Uvh libwbclient-4.18.3-100.el9.x86_64.rpm 2. wc /etc/alternatives/libwbclient.so.0.15-64 3. Actual results: wc: /etc/alternatives/libwbclient.so.0.15-64: No such file or directory Expected results: File does not exist Additional info: I think the preuninstall scriptlet is broken. It says: bash-5.1$ rpm --scripts -q libwbclient preuninstall scriptlet (using /bin/sh): if [ $1 -eq 0 ]; then /usr/sbin/update-alternatives \ --remove \ libwbclient.so.0.16-64 \ /usr/lib64/samba/wbclient/libwbclient.so.0.16 fi /sbin/ldconfig posttrans scriptlet (using /bin/sh): # It has to be posttrans here to make sure all files of a previous version # without alternatives support are removed /usr/sbin/update-alternatives \ --install \ /usr/lib64/libwbclient.so.0.16 \ libwbclient.so.0.16-64 \ /usr/lib64/samba/wbclient/libwbclient.so.0.16 \ 10 I believe the [ $1 -eq 0 ] test means that the alternative is removed only on uninstall, so an upgrade to a new version leaves the dangling symlink behind. Regards, Andy