Debian Patches
Status for debspawn/0.6.4-2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 02_define-dependencies-in-pyproject.toml-only.patch | [PATCH 2/2] Define dependencies in pyproject.toml only Apparently, Debian's tools only look in pyproject.toml now for dependencies if it's present - to not define dependencies twice while still having setup.py around (since we need to install stuff into external locations and check for additional non-Python dependencies) we read pyproject.toml from setup.py. Python packaging for anything that isn't a simple, self-contained library is a mess! |
Matthias Klumpp <matthias@tenstral.net> | no | 2025-05-21 | ||
| 01_fix-package-pinning-for-release-codenames.patch | [PATCH 1/2] Fix package pinning when specifying a suite by its release codename Previously, pinning would work when using something like this: debspawn create --suite=stable-backports --base-suite=stable ... but packages would fail to install when using something like this: debspawn create --suite=bookworm-backports --base-suite=bookworm ... |
Darsey Litzenberger <dlitz@dlitz.net> | no | 2024-05-08 |