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).

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 builpackage --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/mssql-django.git
    cd mssql-django
    gbp buildpackage --git-pbuilder

The upstream source mssql-django is a fork of django-mssql-backend, which
itself is a fork of django-pyodbc-azure. This project was then a fork of
django-pyodbc.
But there is also a old project called django-mssql, that's a bit of an
unfortunate and misleading situation. Nevertheless all these previous forks
seems to be death while writing.

 -- Carsten Schoenert <c.schoenert@t-online.de>, Mon,  1 Nov 2021 10:43:40 +0100
