1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52
|
This package is maintained with git-buildpackage(1). It follows DEP-14 for
branch naming (e.g. using debian/main for the current version in Debian
unstable due Debian Python team policy).
It uses pristine-tar(1) to store enough information in git to generate bit
identical tarballs when building the package without having downloaded an
upstream tarball first.
When working with patches it is recommended to use "gbp pq import" to import
the patches, modify the source and then use "gbp pq export --commit" to commit
the modifications.
The changelog is generated using "gbp dch" so if you submit any changes don't
bother to add changelog entries but rather provide a nice git commit message
that can then end up in the changelog.
It is recommended to build the package with pbuilder using:
gbp buildpackage --git-pbuilder
For information on how to set up a pbuilder environment see the git-pbuilder(1)
manpage. In short:
DIST=sid git-pbuilder create
gbp clone https://salsa.debian.org/python-team/packages/python-lia.git
cd python-lia
gbp buildpackage --git-pbuilder
Disabled tests from the upstream suite
--------------------------------------
Two upstream projects are not packaged in Debian and thus the test suite will
fail if we do not ignore the upstream test files fore these specific tests.
These upstream packages are not within Debian.
chalice https://github.com/aws/chalice
sanic https://github.com/sanic-org/sanic
The debian/rules files is ignoring the following files while running the
usptream tests.
tests/request/test_chalice.py
tests/request/test_litestar.py
tests/request/test_sanic.py
We ignore test_litestar.py for now, the test is failing because it can't find
the module multidict, the missing module while the test is correct, but for a
not known reason the package python3-multidict isn't getting installed even if
this is a dependency of python3-litestar. :-(
-- Carsten Schoenert <c.schoenert@t-online.de> Sat, 1 Nov 2025 13:21:00 +0200
|