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.
Prior to this update, the mksh package did not specify all requirements for RPM scriptlets. As a result, the requirements were not installed during the post install setup and the scriptlets were not able to work correctly. With this update, the bug has been fixed, and the mksh package now specifies the requirements and installs them as expected.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Prior to this update, the mksh package did not specify all requirements for RPM scriptlets. As a result, the requirements were not installed during the post install setup and the scriptlets were not able to work correctly. With this update, the bug has been fixed, and the mksh package now specifies the requirements and installs them as expected.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0923.html
Description of problem: mksh runs /usr/sbin/alternatives in its installation scriplets, but the package doesn't depend on the chkconfig package: [root@rtt6 ~]# rpm --nogpg -q --scripts -p rpms/mksh-39-5.el6.s390x.rpm | grep alternatives /usr/sbin/alternatives --install /bin/ksh ksh \ /usr/sbin/alternatives --remove ksh /bin/mksh [root@rtt6 ~]# rpm -qf /usr/sbin/alternatives chkconfig-1.3.47-1.el6.s390x [root@rtt6 ~]# rpm --nogpg -q --requires -p rpms/mksh-39-5.el6.s390x.rpm | grep chkconfig [root@rtt6 ~]# It causes error messages in some cases: ... Installing : coreutils-8.4-13.el6.s390x 31/33 Installing : pam-1.1.1-8.el6.s390x 32/33 Installing : mksh-39-5.el6.s390x 33/33 Non-fatal POSTIN scriptlet failure in rpm package mksh-39-5.el6.s390x /var/tmp/rpm-tmp.4KwYIK: line 4: /usr/sbin/alternatives: No such file or directory warning: %post(mksh-39-5.el6.s390x) scriptlet failed, exit status 127 Version-Release number of selected component (if applicable): mksh-39-5.el6 How reproducible: always Steps to Reproduce: 1. yum --installroot=/root/new_install_root install mksh Actual results: errors during installation Expected results: mksh depends on chkconfig, no error messages during installation