Description of problem: The latest version of the Linux Standard Base Core Specification (e.g. https://refspecs.linuxfoundation.org/LSB_5.0.0/LSB-Core-AMD64/LSB-Core-AMD64/libcrypt.html) says that libcrypt.so.1 is part of the Core Specification. As part of glibc deprecating libcrypt and Fedora (and possibly sibling distros) transitioning to libxcrypt, libcrypt.so.1 seemed to have been dropped by the Fedora base install. In order to get libcrypt.so.1 and be in stronger compliance with the LSB Core Specification, you need to install the libxcrypt-compat package. Version-Release number of selected component (if applicable): How reproducible: Always. Part of base OS install and official container images. Steps to Reproduce: 1. Install Fedora 35 Actual results: No libcrypt.so.1 in base install. Expected results: libcrypt.so.1 should be in base install and provide the interfaces defined by the LSB Core Specification. Additional info: https://refspecs.linuxfoundation.org/LSB_5.0.0/LSB-Core-AMD64/LSB-Core-AMD64/baselib.html says "shall support base libraries." "shall" is not "must" so there is some wiggle room to not contain libcrypt.so.1 by default. However, I believe Fedora is currently an outlier, as other popular distros seem to be providing libcrypt.so.1 and in better compliance with the LSB Core Specification. Also, `dnf install redhat-lsb-core` does not install libxcrypt-compat. That's potentially another oversight. https://github.com/indygreg/python-build-standalone/issues/113 describes a real world implication to Fedora not providing libcrypt.so.1 out-of-the-box.
Changing to redhat-lsb package, as this should require libxcrypt-compat; see [1] for a PR fixing this. [1] https://src.fedoraproject.org/rpms/redhat-lsb/pull-request/6
Gentle ping on this issue. Does RedHat consider this a bug?
FEDORA-2022-e4e62f0329 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e4e62f0329
FEDORA-2022-e4e62f0329 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.