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
|
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-sphobjinv.git
cd python-sphobjinv
gbp buildpackage --git-pbuilder
Vendored variant of fuzzywuzzy source code included
===================================================
Upstream is using some vendored code in the folder
src/sphobjinv/_vendored/fuzzywuzzy
According to the information from the file
src/sphobjinv/_vendored/fuzzywuzzy/__init__.py
the main reason to use a vendored copy was a license change from MIT to GPL-2+
that did happen to one file in the fuzzywuzzy source afterwards.
There is a source package fuzzywuzzy available in Debian:
https://tracker.debian.org/pkg/fuzzywuzzy
But we can't use that variant to not use vendored code as the codebase differs
now to much.
-- Kathara Sasikumar <katharasasikumar007@gmail.com> Thu, 25 Jul 2024 21:36:00 +0530
|
