libcrypt.so.1 should be provided as an AUR package, and not in glibc.

Hi again,
severity can be lowered because there is a workaround:
install libxcrypt and add link /usr/lib/libcrypt.so.1 to point to /usr/lib/libcrypt.so
I don't know if the APIs are 100% compatible, but at least the applications starts and seems functional.

It looks like libxcrypt is binary backwards compatible, citing the project README.md:
https://github.com/besser82/libxcrypt

"""
Compatibility Notes
On Linux-based systems, by default libxcrypt will be binary backward compatible with the libcrypt.so.1 shipped as part of the GNU C Library. This means that all existing binary executables linked against glibc’s libcrypt should work unmodified with this library’s libcrypt.so.1. We have taken pains to provide exactly the same symbol versions as were used by glibc
"""

So, adding the link /usr/lib/libcrypt.so.1 pointing to libcrypt.so looks like a proper solution.

I've got the PKGBUILD ready to upload to the AUR.
Please, can you confirm this is still the preferred solution?

pkgname=libcrypt
pkgver=1
pkgrel=0
pkgdesc='provides glibc libcrypt from libxcrypt'
arch=('any')
depends=('libxcrypt')
package() {
mkdir -p "${pkgdir}/usr/lib"
ln -s 'libcrypt.so' "${pkgdir}/usr/lib/libcrypt.so.1"
}

> Please, can you confirm this is still the preferred solution?

no.

we already have libxcrypt-compat[1] in aur.
please use that.

[1] https://aur.archlinux.org/packages/libxcrypt-compat

btw you can also download it from my repo.

[alex19EP]
Server = https://pkgbuild.com/~alex19ep/repo/$arch

Ok, got it working, although libxcrypt-compat does not build without adding --disable-werror to the configure command.

Thank you for your support!

Hi @alex19EP, i've tried building your version and it also fails to build without --disable-werror.
Once build, it fails one of the checks:
*** Missing symbol versions:
crypt_gensalt@GLIBC_2.2.5
crypt_gensalt@OW_CRYPT_1.0
crypt_gensalt_ra@GLIBC_2.2.5
crypt_gensalt_ra@OW_CRYPT_1.0
crypt_gensalt_rn@GLIBC_2.2.5
crypt_gensalt_rn@OW_CRYPT_1.0
crypt_ra@GLIBC_2.2.5
crypt_rn@GLIBC_2.2.5
FAIL test/symbols-compat.pl (exit status: 1)

Is this related to your build options or should this be reported upstream?

`libxcrypt-compat` builds fine for me from AUR.