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:

When sourcing /etc/kshrc from a non interactive ksh shell an error is produced from /etc/profile.d/which2.sh .

This does not occur for which-2.21-12.el8.x86_64 .

Version-Release number of selected component (if applicable): which-2.21-16.el8.x86_64


How reproducible: always


Steps to Reproduce:
1. Create test script test.ksh

    #!/bin/ksh
    . /etc/kshrc

2. Run ./test.ksh

Actual results:

    ./test.ksh
    ./test.ksh[6]: .[17]: .[19]: export: -f: unknown option
    Usage: export [-p] [name[=value]...]

Expected results:

    ./test.ksh

it ist fixed in which-2.21-17

I have tried to upgrade to which-2.21-17.  This package does not appear to be available yet.  Can you confirm when it will be released?

*** This bug has been marked as a duplicate of bug 2009547 ***

Do not believe this is a duplicate of bug 2009547 (https://bugzilla.redhat.com/show_bug.cgi?id=2009547).

Spoke to Donald, he agrees.