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-minijinja.git
    cd python-minijinja
    gbp buildpackage --git-pbuilder


Repacked source code tarball
----------------------------

The upstream source code for the Python library is included in the tarball
for all MiniJinja components and available on the home of the project on
GitHub.

  https://github.com/mitsuhiko/minijinja/tags

As we are not interessted in all parts of the upstream source we do a clean
out of all files and folders we don't need for building the binary package.
This is done in the section [import-orig] by the postunpack hook of
git-buildpackage.

Have a look at the small helper script debian/repack-minijinja-py.sh for
details.

Basically every file in the top folder of the archive is gonna through away as
also every folder except a folder named 'minijinja-py'. Finally the content of
the folder 'minijinja-py' is moved into the top folder and the folder is also
getting removed.


 -- Carsten Schoenert <c.schoenert@t-online.de>  Sat, 25 Jan 2025 14:55:00 +0200
