vcswatch reports that
this package seems to have a new changelog entry (version
0.7.8-4, distribution
unstable) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Here are the relevant commit messages:
commit bf0ead2c0c383101335a42f0d70fef409d9cb892
Author: Dustin Kost <dustin.kost@gmail.com>
Date: Fri Aug 14 08:24:19 2026 +0000
Prepare 0.7.8-4: adopt into the team, and act on what lintian reported
Adoption entry closing #1093669, with myself in Uploaders. The package had the
team as Maintainer and nobody in Uploaders, which lintian reports as
E: no-human-maintainers and which is what failed the Salsa CI lintian job.
Drop debian/upstream/signing-key.asc. It produced two warnings and could never
be used: PyPI reports no OpenPGP signature for any rply release, having
dropped signature support entirely in 2023, and the upstream git tags are
lightweight rather than annotated, so pgpmode=gittag has nothing to verify
either. lintian's own advice for this case is to enable verification or remove
the key, and enabling it is not possible here.
Rewrite debian/watch with the version 5 PyPI template, which supplies the same
base URL, plain searchmode and uversionmangle that the v3 file spelled out by
hand, and records pgpmode=none explicitly. uscan confirms it resolves and
reports the package up to date at 0.7.8.
Drop Rules-Requires-Root: no, which dpkg has defaulted to since 1.22.13;
unstable carries 1.23.7.
Correct the description, which misspelled the author of PLY, David Beazley, as
"Bazzley". The upstream README has it right.
debhelper-compat stays at 14. Worth recording why, because the host and the
target suite disagree and the host is the misleading one: the
debhelper-compat-upgrade-checklist installed here comes from debhelper 13.24.2
and still calls v14 "open for development", but unstable ships debhelper 14.3,
and lintian 2.139.0 in an unstable chroot emits
package-uses-old-debhelper-compat-version against compat 13. The suite being
targeted is the one whose toolchain counts.
Remaining known-imperfect, both deliberate and to be disclosed in the RFS: the
PyPI sdist ships no tests - upstream keeps them in git but MANIFEST.in
excludes them - so the autopkgtest is autodep8's superficial import check; and
the package still installs legacy .egg-info because upstream provides no
pyproject.toml to convert to pybuild-plugin-pyproject.
commit 38fa79a9985935271256ab03945ec608a6d7ed45
Author: Dustin Kost <dustin.kost@gmail.com>
Date: Mon Aug 10 18:50:53 2026 +0000
Add debian/salsa-ci.yml
Makes the CI pipeline explicit and part of the source package, rather than
depending on a GitLab project setting that only exists on salsa. Mirrors the
configuration already used by python-svg.path.
blhc and the separate arch-all/arch-any build jobs are disabled: this is a
pure-Python arch:all package, so there is no compiled code to check hardening
flags on and those jobs only duplicate the main build.
commit 2e0517c86430df9d1a89e7a2c78b24a522ff7c63
Author: Dustin Kost <dustin.kost@gmail.com>
Date: Mon Aug 10 01:56:29 2026 +0000
Modernise packaging
debhelper-compat 13 -> 14, Standards-Version 4.7.0 -> 4.7.4, and drop the
Priority field from the source stanza - 4.7.3 stopped recommending it.
The other normative changes across 4.7.1-4.7.4 are N/A for an arch:all pure
Python library in main: no shared libraries, no daemons, nothing installed
outside /usr/lib and /usr/share, no /usr/games.
https://salsa.debian.org/api/v4/projects/python-team%2Fpackages%2Fpython-rply API request failed: 401 Unauthorized at /srv/qa.debian.org/data/vcswatch/vcswatch line 410.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/p/python-rply.png){kind=link}