FS#79150 - [python-hatch] Incorrect dependencies makes hatch unusable
Attached to Project:
Arch Linux
Opened by KRACKY (KRACKY) - Wednesday, 19 July 2023, 18:31 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 19 July 2023, 18:44 GMT
Opened by KRACKY (KRACKY) - Wednesday, 19 July 2023, 18:31 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 19 July 2023, 18:44 GMT
|
Details
Description: `hatch` constantly breaks in almost all use
cases, since its dependencies are incorrect. These include,
but are not limited to:
- `hatch new` in a new project - `hatch build` in a current project - `hatch shell` in a current project Additional info: * package version: 1.7.0-2 * duplicate of https://bugs.archlinux.org/task/79142 , but I increased its priority accordingly (see comments for justification) Steps to reproduce: 1. Get a clean Arch installation, with no currently installed python dependencies (e.g. `docker run --rm -it --init archlinux`) 2. install this package (e.g. `pacman -S python-hatch`) 3. run any of the above commands --- I have already taken the liberty to comparing the arch PKGBUILD dependencies against the pyproject.toml dependencies upstream (https://github.com/pypa/hatch/blob/master/pyproject.toml), and listed them as below. Moreover, note that some will already be auto-installed as dependencies of those already included, but it may be best to make all dependencies of hatch explicit in case any of the other arch packages change their own dependency files in the future. --- Not indirectly installed: - `python-httpx` - `python-hyperlink` - `python-shellingham` - `python-tomli-w` indirectly installed, but not yet explicit: - `python-keyring` - `python-packaging` - `python-platformdirs` |
This task depends upon
However, this just redirects to the actual upstream file of https://github.com/pypa/hatch
This is also where the actual repo is being installed from, if I am correctly reading this https://gitlab.archlinux.org/archlinux/packaging/packages/python-hatch/-/blob/1.7.0-2/PKGBUILD