File: README.source

package info (click to toggle)
python-validate-pyproject 0.24.1-1
  • links: PTS, VCS
  • area: main
  • in suites: sid, trixie
  • size: 1,340 kB
  • sloc: python: 3,053; makefile: 46; sh: 25
file content (43 lines) | stat: -rw-r--r-- 1,706 bytes parent folder | download
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
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/validate-pyproject.git
    cd validate-pyproject
    gbp buildpackage --git-pbuilder


Use of local sphinx inventory for -doc package
----------------------------------------------
Where possible we use object.inv files from packages which provide the data.
Unfortunately not all required files can get included, the following upstream
project is disabled in docs/conf.py by patching that file.

pyscaffold, not packaged in Debian

Also one sphinx extension is not available and got disabled by the patch
queue in docs/conf.py.

sphinx-jsonschema        https://github.com/lnoor/sphinx-jsonschema

 -- Carsten Schoenert <c.schoenert@t-online.de>  Thu, 20 Mar 2024 18:12:00 +0200