Missing Dependency on libcrypt.so.1 for Python 3.11 in Arch Linux

[aemonge]

Checklist

• I have searched the Sourcery documentation for the issue, and found nothing
• I have checked there are no open bugs referencing the same bug or problem

Description

I've encountered an issue while trying to run Sourcery on my Arch Linux setup. The application appears to have a dependency on libcrypt.so.1, but only libcrypt.so.2 is available on my system. This results in an error preventing the application from running. Expected behavior: Sourcery should run without requiring older versions of shared libraries or producing related errors.

Code snippet that reproduces issue

The error message I received is:

/home/deck/.conda/envs/helios/lib/python3.11/site-packages/sourcery/sourcery:
error while loading shared libraries: libcrypt.so.1: cannot open shared
object file: No such file or directory

Debug Information

IDE Version:
CLI

Sourcery Version:
sourcery-cli = "^1.8.0"

❯ pip install sourcery-cli
Requirement already satisfied: sourcery-cli in /home/deck/.conda/envs/helios/lib/python3.11/site-packages (1.8.0)

Operating system and Version:
Arch Linux (5.13.0-valve36-1-neptune)
Python Version: 3.11 (Conda environment)

     active environment : helios
    active env location : /home/deck/.conda/envs/helios
            shell level : 4
       user config file : /home/deck/.condarc
 populated config files : /home/deck/.condarc
          conda version : 23.5.2
    conda-build version : not installed
         python version : 3.11.4.final.0

Install libxcrypt

❯   sudo pacman -S --needed --noconfirm libxcrypt

[sudo] password for deck: 
warning: libxcrypt-4.4.28-2 is up to date -- skipping
 there is nothing to do

Running sourcery

❯ sourcery -h
/home/deck/.conda/envs/helios/lib/python3.11/site-packages/sourcery/sourcery: error while loading shared libraries:
libcrypt.so.1: cannot open shared object file: No such file or directory

[ruancomelli]

Hello, @aemonge! Thanks for reaching out!

Is it feasible for you to install libxcrypt-compat? This is normally the fix for this issue on unsupported Linux distros. Please let me know if this is possible and if it fixes the issue for you.

[aemonge]

Woho !

I'm back baby !

Thanks @ruancomelli