This package is maintained with git-buildpackage(1). It follows DEP-14 for
branch naming (e.g. using debian/master 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-advanced-alchemy.git
    cd python-advanced-alchemy
    gbp buildpackage --git-pbuilder


No execution of tests while package build or in autopkgtest
-----------------------------------------------------------

Upstream is using a docker container which is getting pulled within the test.
Maybe we can place a copy of this container later within the debian/ folder but
this would still be very fragile to maintain over time. So running upstream
tests is an unsolved issue right now.

Optional needed packages for tests
----------------------------------

Beside the test suite is based on a docker container right now some additional
packages would be needed to be available in the archive.

src:sqlalchemy-cockroachdb https://github.com/cockroachdb/sqlalchemy-cockroachdb
src:python-asyncpg https://github.com/MagicStack/asyncpg


-- Carsten Schoenert <c.schoenert@t-online.de>  Sat, 04 Jan 2025 09:50:00 +0200
