Dear mentors,

I am looking for a sponsor for my package "python-svg.path":

 * Package name     : python-svg.path
   Version          : 7.1-1
   Upstream contact : Lennart Regebro <regebro@gmail.com>
 * URL              : https://github.com/regebro/svg.path
 * License          : Expat (tests/font.py: HPND)
 * Vcs              : https://salsa.debian.org/python-team/packages/python-svg.path
   Section          : python

The source builds the following binary package:

  python3-svg.path - SVG path objects and parser for Python3

To access further information about this package, please visit the following URL:

https://mentors.debian.net/package/python-svg.path/

Alternatively, you can download the package with 'dget' using this command:

  dget -x https://mentors.debian.net/debian/pool/main/p/python-svg.path/python-svg.path_7.1-1.dsc

Changes since the last upload:

 python-svg.path (7.1-1) unstable; urgency=medium
 .
   * New upstream release.
     - Reset cached segment fractions when a Path is re-measured, fixing wrong
       coordinates or an IndexError from point()/tangent() after mutating a Path
       via del/setitem/insert/slice assignment.
     - Add Path.lengths().
     - Better handling of tangents of paths that start with a Move().
   * Adopt the package under the Debian Python Team umbrella (Closes: #816512).
   * Bump Standards-Version to 4.7.4 (no changes needed).
   * Bump debhelper-compat to 14; none of its changes affect this package.
   * Drop the unused debian/tests/python3-svg.path script. There is no
     debian/tests/control, so nothing ever ran it; the autopkgtest is
     generated from Testsuite: autopkgtest-pkg-pybuild. It also invoked
     "setup.py test", which setuptools no longer supports.
   * debian/copyright: extend the upstream copyright range to 2026, the code
     having been modified through 7.1, and add myself to the debian/* stanza.

Some context, since this is my first upload.

The package has been orphaned since 2017 (#816512, filed as an RFA in 2016 by
Daniel Stender and orphaned the following year for lack of time). I have
retitled the bug to ITA and taken ownership. Alexandre Detiste did a QA upload
in January 2026 which left the packaging in good shape, so this upload is
mostly the pending upstream release plus the adoption itself.

Following Debian Python Team policy I have set Maintainer to the team and put
myself in Uploaders. My salsa account is awaiting approval, so I have not yet
been able to push to the team repository or run the Salsa CI pipeline; the
branches are ready locally and I will push as soon as I have access. I will
also be requesting team membership on debian-python@lists.debian.org.

QA performed, all against unstable:

  * sbuild in a clean sid chroot: successful
  * lintian 2.139.0 (run inside the chroot), --info --display-info --pedantic:
    no tags at all. For comparison, 7.0-2 as it stands in the archive emits
    orphaned-package-maintained-in-private-space, which this upload resolves.
  * autopkgtest (unshare backend, sid): pass, 56 tests on Python 3.14.6
  * piuparts: pass for install, upgrade and purge
  * debdiff against 7.0-2 reviewed; the debian/ changes are limited to
    debian/changelog, debian/control and the removed debian/tests script

The changelog has six entries where the adoption alone would have needed two.
If you would prefer a narrower first upload, the debhelper-compat bump and the
removal of the dead debian/tests script are both independent of the adoption,
and I am happy to drop them and submit them separately.

Regards,
--
Dustin Kost

The package now has a green Salsa CI pipeline on my fork:
https://salsa.debian.org/dkost/python-svg.path/-/pipelines/1147181

All jobs pass: build (amd64 + i386), build source, lintian, autopkgtest,
piuparts, debrebuild and test-uscan.

My salsa account was approved today, so the packaging branches are now
pushed and reviewable at:
https://salsa.debian.org/dkost/python-svg.path

I am still awaiting Debian Python Team membership, so I cannot push to
the team repository directly, happy to open a merge request instead if
that is easier to review.

Thanks,
Dustin

#1144088, ITA #1067786 closed).

This one is still looking for a sponsor. Nothing about the package has
changed since the original upload; it is the same 7.1-1, with the same
evidence:

https://salsa.debian.org/python-team/packages/python-svg.path
https://salsa.debian.org/python-team/packages/python-svg.path/-/pipelines/1147371

lintian 2.139.0 reports no tags inside a sid chroot, autopkgtest passes 56
tests, piuparts passes install, upgrade and purge.

Regards,
Dustin Kost

Hello,

Please try to address this Lintian output on your next upload:

Running lintian...
N:
I: python3-svg.path: package-contains-documentation-outside-usr-share-doc [usr/lib/python3/dist-packages/svg_path-7.1.dist-info/top_level.txt]
N:
N:   This package ships a documentation file outside /usr/share/doc
N:   Documentation files are normally installed inside /usr/share/doc.
N:
N:   If this file doesn't describe the contents or purpose of the directory it
N:   is in, please consider moving this file to /usr/share/doc/ or maybe even
N:   removing it. If this file does describe the contents or purpose of the
N:   directory it is in, please add a lintian override.
N:
N:   Visibility: info
N:   Show-Always: no
N:   Check: documentation
N:
N:   Screen: python/egg/metadata
N:     Advocates: "Scott Kitterman" <debian@kitterman.com>
N:     Reason: The folders XXX.dist-info/ and XXX.egg-info/ hold metadata for
N:             Python modules. Those files are not documentation even though
N:             some of their names carry the .txt file extension.
N:
N:             Python modules can be both public and private.
N:
N:             Read more in
N:             https://www.python.org/dev/peps/pep-0427/#the-dist-info-directory,
N:             https://www.python.org/dev/peps/pep-0376/#id16,
N:             https://www.python.org/dev/peps/pep-0610/,
N:             https://www.python.org/dev/peps/pep-0639/,
N:             https://setuptools.pypa.io/en/latest/deprecated/python_eggs.html,
N:             and Bug#1003913.
N:
N:
X: python-svg.path source: debian-watch-does-not-check-openpgp-signature [debian/watch]
N:
N:   This watch file does not specify a means to verify the upstream tarball
N:   using a cryptographic signature.
N:
N:   If upstream distributions provides such signatures, please use the
N:   pgpsigurlmangle options in this watch file's opts= to generate the URL of
N:   an upstream OpenPGP signature. This signature is automatically downloaded
N:   and verified against a keyring stored in debian/upstream/signing-key.asc
N:
N:   Of course, not all upstreams provide such signatures but you could request
N:   them as a way of verifying that no third party has modified the code after
N:   its release (projects such as phpmyadmin, unrealircd, and proftpd have
N:   suffered from this kind of attack).
N:
N:   Please refer to the uscan(1) manual page for details.
N:
N:   Visibility: pedantic
N:   Show-Always: no
N:   Check: debian/watch
N:   Renamed from: debian-watch-does-not-check-gpg-signature
N:   debian-watch-may-check-gpg-signature
N:   This tag is experimental.
N:

I: Lintian run successful (worst tag: info)

Otherwise, enjoy:

$ dput ftp-master ../python-svg.path_7.1-1_source.changes
Uploading python-svg.path using ftp to ftp-master (host: ftp.upload.debian.org; directory: /pub/UploadQueue/)
running allowed-distribution: check whether a local profile permits uploads to the target distribution
running protected-distribution: warn before uploading to distributions where a special policy applies
running checksum: verify checksums before uploading
running suite-mismatch: check the target distribution for common errors
running gpg: check GnuPG signatures before the upload
Uploading python-svg.path_7.1-1.dsc
Uploading python-svg.path_7.1.orig.tar.gz
Uploading python-svg.path_7.1-1.debian.tar.xz
Uploading python-svg.path_7.1-1_source.buildinfo
Uploading python-svg.path_7.1-1_source.changes

Best regards,
Simon Quigley
tsimonq2@debian.org