Closed issue by zlice on void-packages repository

https://github.com/void-linux/void-packages/issues/46821

Description:
### Is this a new report?

Yes

### System Info

Void 6.5.7 x86_64 AuthenticAMD notuptodate rFFFFFFFFF

### Package(s) Affected

pip, python

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

pip detects proper packages and installs

### Actual behaviour

```
error: externally-managed-environment

× This environment is externally managed
╰─> 
    This system-wide Python installation is managed by the Void Linux package
    manager, XBPS. Installation of Python packages from other sources is not
    normally allowed.
    
    To install a Python package not offered by Void Linux, consider using a virtual
    environment, e.g.:
    
    python3 -m venv /path/to/venv
    /path/to/venv/pip install <package>
    
    Appending the flag --system-site-packages to the first command will give the
    virtual environment access to any Python package installed via XBPS.
    
    Invoking python, pip, and executables installed by pip in /path/to/venv/bin
    should automatically use the virtual environment. Alternatively, source its
    activation script to add the environment to the command search path for a shell:
    
    . /path/to/venv/activate
    
    After activation, running
    
    deactivate
    
    will remove the environment from the search path without destroying it.
    
    The XBPS package python3-pipx provides pipx, a convenient tool to automatically
    manage virtual environments for individual Python applications.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
```

### Steps to reproduce

1. `xbps-install dlib`
2. `xbps-remove dlib`
3. `pip install dlib`

Did a `pip install dlib --break-system-packages` between 1 and 2 before remove, not sure if that matters