DFSG NEW review for python-run-isolated version 0.1.3-1

Summary

• Licensing is DFSG-compliant and debian/copyright is accurate: Yes
• Packaging is of good quality: Yes
• Issues: 0 blocker, 0 important, 0 minor
• debian/watch: version 5
• debian/copyright: machine-readable
• Scan before the review: nothing found

Licensing

debian/copyright is DEP-5, names the single holder (Peter Pentchev) in both its Files: * and Files: debian/* stanzas, and uses BSD-2-clause with the full licence text. Every file in the upstream tree carries a matching SPDX-FileCopyrightText: Peter Pentchev <roam@ringlet.net> / SPDX-License-Identifier: BSD-2-Clause header, REUSE.toml annotates the one file (uv.lock) without a header with the same licence, and the pre-review author check found no unnamed holder. BSD-2-clause is free, the permissive notice is reproduced in full, and there is no non-free or field-of-use wording anywhere in the tree.

Packaging

A clean, conventional Debian Python Team package: pybuild with pyproject/hatchling at debhelper compat 14 (current recommended level) with dpkg-build-api 1, one arch:all binary package, correct build and runtime dependencies, DEP-3-free tree with no patches, an autopkgtest that exercises the module under every installed Python, a salsa-ci pipeline, upstream metadata and a commented lintian override for the year-less copyright notices. Standards-Version 4.7.4 matches the reviewing system's Policy 4.7.4.1; the changelog targets experimental for this initial NEW upload, which is a legitimate choice.

Issues

None.

Verified

• debian/copyright read in full: DEP-5 format, Upstream-Name, Source, Files: * (Peter Pentchev roam@ringlet.net) and Files: debian/* (Peter Pentchev roam@debian.org), both BSD-2-clause, with the complete BSD-2-clause text in the stand-alone License paragraph; no /usr/share/common-licenses pointer is needed.
• Sampled every upstream text file, then confirmed by grep over the whole tree (gitignore disabled): all of .gitignore, .readthedocs.yaml, README.md, REUSE.toml, mkdocs.yml, pyproject.toml, ruff-base.toml, tox.ini, .builds/.yml, docs/.md, requirements/docs.txt, src/run_isolated/.py, tests/run-uvoxen.sh and tests/unit/.py carry SPDX-License-Identifier: BSD-2-Clause and the same holder; no other copyright holder, licence or provenance wording (based on, adapted from, non-commercial, Good, not Evil) appears anywhere.
• Pre-review author check (dfsg-author-check) scanned 29 files and reported that every holder found is named in debian/copyright; I reached the same conclusion from the SPDX headers.
• PKG-INFO is generated from pyproject.toml (which is in the tree); tox.ini and requirements/docs.txt are generated from the [tool.uvoxen] configuration in pyproject.toml, so the preferred form of each is present. No built HTML, PDF, bytecode, minified code or archives are shipped; docs/*.md are hand-written sources.
• uv.lock is a metadata lock file (package names, versions, URLs and hashes only, no copied code); REUSE.toml annotates it with SPDX-License-Identifier = "BSD-2-Clause" and pyproject.toml is its generator input.
• LICENSES/BSD-2-Clause.txt is the REUSE licence-text file, whose Copyright (c) <year> <owner> line is a placeholder, not a third-party copyright claim; it is covered by Files: *.
• src/run_isolated/py.typed is an empty marker file, covered by Files: * under BSD-2-clause.
• debian/control checked against apt-cache: python3-pshlex 0.1.1 in unstable satisfies upstream's pshlex >= 0.1, < 0.2; pybuild-plugin-pyproject is in unstable; dh-sequence-single-binary is provided by debhelper 14.5, so Build-Depends is satisfiable. python3-pytest 9.1.1 in unstable depends on python3-packaging, which the unit tests import, so the build and the autopkgtest have everything they need.
• debhelper tool checked for compat 14: the implicit single-binary add-on that the package activates explicitly with dh-sequence-single-binary is the compat-14 behaviour, and dh skips the override_dh_auto_test target under nocheck, so the missing nocheck guard there is not a fault; relationship substvars need not be listed at compat 14.
• debian/rules passes --test-pytest/--test-args to pybuild (both are documented pybuild options, man pybuild), and --strict is still a registered pytest option in the installed pytest 9.x, so the override is valid.
• dpkg-build-api (= 1) is the recommended level per dpkg-build-api(7) and makes Rules-Requires-Root default to no; debhelper-compat (= 14) is the recommended compat level per debhelper-compat-upgrade-checklist(7).
• No debian/patches and no debian/patches/series, so the 3.0 (quilt) format carries no patches; no maintainer scripts, no *.maintscript, no .install/.links/.docs files that could be wrong.
• Standards-Version 4.7.4 against the reviewing system's Policy 4.7.4.1: same first two components, so not an issue.
• debian/tests/control: valid autopkgtest stanza, Depends covers python3-all, python3-pytest and the build-dependencies via @; the docker/schroot tests skip themselves without the TEST_RUN_ISOLATED_* environment variables, so the test passes without docker, podman or schroot.
• uscan found the packaged version as the newest upstream release (upstream 0.1.3, packaged 0.1.3).

Not confirmed

None.

Proposed changes

None.