gputaskman 0.4.1-1

Package Information

Description	GPU task manager A GPU task manager with per-process VRAM, GPU activity, and LLM model/KV-cache insights.
Maintainer	Daniel Baumann <daniel@debian.org>
Changed By	Daniel Baumann <daniel@debian.org>
Sponsor	mail@daniel-baumann.ch
Distribution	sid
Architecture	all
VCS	git: https://forgejo.debian.net/linux/gputaskman (browse)
Tracker	https://tracker.debian.org/pkg/gputaskman
Uploaded	2 hours ago

New Package Report

.changes◂

Changed-By	Daniel Baumann <daniel@debian.org>
Architecture	source all
Distribution	sid
Date	Sun, 15 Nov 2026 03:27:01 +0100
Source	gputaskman
Version	0.4.1-1

Changelog◂

gputaskman (0.4.1-1) sid; urgency=medium
 .
   * Initial upload to sid.

.dsc◂

Section	utils
Priority	optional
Component	main
Package-List	gputaskman deb utils optional arch=all

debian/copyright◂

Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: gputaskman
Upstream-Contact: https://github.com/shanselman/gputaskman/issues
Source: https://github.com/shanselman/gputaskman/tags

Files: *
Copyright: 2026 Scott Hanselman
License: MIT

Files: debian/*
Copyright: 2026 Daniel Baumann <daniel@debian.org>
License: MIT

License: MIT
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
 in the Software without restriction, including without limitation the rights
 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 copies of the Software, and to permit persons to whom the Software is
 furnished to do so, subject to the following conditions:
 .
 The above copyright notice and this permission notice shall be included in
 all copies or substantial portions of the Software.
 .
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.

DFSG Assistant LLM REVIEW 0 blocker, 1 important, 1 minor

This is an LLM based review using a Debian Inference based workflow. It was not written by a member of the DFSG team and has not been checked by one. It is not a decision on the package: it may be wrong, and it may have missed things.

Reviewed 0 hours ago.

Report◂

DFSG NEW review for gputaskman version 0.4.1-1

Summary

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

Licensing

debian/copyright is valid DEP-5 and accurate: every upstream file is MIT, held by Scott Hanselman, matching the root LICENSE (Copyright (c) 2026 Scott Hanselman) and pyproject's license = "MIT"; debian/* is MIT held by Daniel Baumann. The full MIT text is included (MIT is not in /usr/share/common-licenses), no file carries another licence or holder, and nothing is vendored. No DFSG problem and no missing licence.

Packaging

The packaging is otherwise modern and clean: debhelper compat 14 with dh sequences, pybuild/pyproject build, no patches, 3.0 (quilt), correct changelog, upstream metadata, current Standards-Version, and correct use of debhelper's automatic relationship substvars. Two things fall short. Upstream's hard runtime dependency nvidia-ml-py (module pynvml) has no Debian package, and without it the entire NVIDIA backend silently does nothing, so the shipped program cannot deliver the per-process VRAM it advertises on NVIDIA hardware. And there is no autopkgtest, so the upstream unittest suite is never run in Debian.

Issues

important packaging 1. NVIDIA backend needs nvidia-ml-py/pynvml, which Debian does not have and the package does not declare ◂

Files: debian/control, pyproject.toml:22, src/gputaskman/linux.py:23-26, src/gputaskman/nvml.py:7-10
Basis: checked, in the package or with a reference tool
Evidence: pyproject.toml:22 "nvidia-ml-py>=13.615.71",; linux.py:23-26 try: / import pynvml as N / except ImportError: # pragma: no cover / N = None; nvml.py:7-10 the same. apt-cache show python3-pynvml, python3-nvidia-ml-py, python3-nvml: no such package, and not in the NEW queues. /usr/share/dh-python/dhpython/pydist.py guess_dependency() returns None for a Requires-Dist name pydist does not know, and /usr/share/dh-python/dist/cpython3_fallback has no nvidia-ml-py line (it does have psutil python3-psutil and textual python3-textual).
Problem: Upstream declares nvidia-ml-py as a hard dependency, and both NVIDIA paths (native Linux in linux.py, and WSL) go through pynvml; without it N is None and NVIDIA GPUs are not enumerated or attributed at all, while only AMD/Intel work via DRM. dh_python3 will therefore not generate any Depends for it (it only translates Requires-Dist names known to pydist), so debian/control silently ships a GPU task manager whose NVIDIA support is dead on Debian, contrary to its Description ('per-process VRAM, GPU activity'). This is a functional gap a sponsor would require resolved before an initial upload.
Fix: Package nvidia-ml-py (as python3-pynvml or similar, the module is pynvml) and add it to the binary package's Depends, or, if that is out of scope for this upload, state in the package description/README that NVIDIA support is unavailable in Debian and add the dependency when the binding is accepted.

minor packaging 2. No autopkgtest: the hardware-independent upstream test suite is never run in Debian ◂

Files: debian/, tests/
Basis: checked, in the package or with a reference tool
Evidence: debian/ contains only changelog, control, copyright, rules, source/format, upstream/metadata and watch; there is no debian/tests/control and no test target in debian/rules (dh $@ --buildsystem=pybuild). tests/ holds 16 unittest modules (test_core.py is 115 KB), and AGENTS.md states 'Tests are hardware-independent (mocks and replayed measurements). CI runs them on Windows, Ubuntu, and macOS with Python 3.11 and 3.13.'
Problem: A substantial, deterministic test suite exists but nothing in the package runs it, so regressions after upload go unnoticed and the package contributes no test to the archive. This is a real testing gap, not a formality, given the amount of platform-specific parsing code.
Fix: Add debian/tests/control (e.g. Tests: unittests, Depends: @, python3-psutil, python3-textual) and a test running python3 -m unittest discover -s tests from the source tree, or wire it through pybuild's autopkgtest support.

Verified ◂

Read every file under debian/ in full: DEP-5 debian/copyright with Files: * (2026 Scott Hanselman, MIT) and Files: debian/* (2026 Daniel Baumann, MIT), and the full MIT licence text, which matches the root LICENSE and pyproject.toml's license = "MIT" / license-files = ["LICENSE"].
Grepped the whole tree with gitignore: false for Copyright, (C), ©, SPDX-License-Identifier, Licensed under, Permission is hereby granted, All rights reserved, GNU ... Public, Apache License, BSD, MPL, public domain, non-commercial wording. Only LICENSE, debian/copyright, and test fixtures match: tests/test_portable.py:37 (fake notice text) and tools/build_portable.py:136 (checks for a notice header). No other holder or licence exists in the tree, so no Files stanza is missing.
Prescan hit tools/build_portable.py:87: if is_forbidden(path.name): raise ValueError(f"Driver/system library must not be distributed: ..."). FORBIDDEN is nvml.dll, libnvidia-ml.so, libcuda.so, amd_smi.dll, etc. — it is a code guard keeping GPU driver libraries out of the portable PyInstaller archive, not a distribution restriction on the software, and the file is MIT.
docs/screenshots/{compositor,help,overview,system-memory}.png are recorded as upstream TUI screenshots referenced by the README; not opened (binary images), covered by Files: * MIT. tools/capture_screenshots.py is their capture script.
No LICENSE/COPYING/NOTICE/AUTHORS files below the root, no vendored code, no embedded third-party library: uv.lock and flake.lock are lockfiles only and tools/portable.spec/tools/portable_entry.py are upstream build files.
At debhelper compat 14 dh_gencontrol adds relationship substvars itself, so the absence of a Depends field in debian/control is not a fault; dh_python3 will derive python3-psutil and python3-textual from the wheel's Requires-Dist via pydist (both mapped in /usr/share/dh-python/dist/cpython3_fallback), and both exist in the archive at versions satisfying upstream's minimums (7.2.2-3 and 8.2.8-1).
Standards-Version: 4.7.4 against the reviewing system's Policy 4.7.4.1: current (first two components match). Source format 3.0 (quilt), no debian/patches and no Files-Excluded, so nothing in the tree is a patch-created or excluded file. Changelog 0.4.1-1 with a valid date ('Sun, 15 Nov 2026' is a Sunday); no bug closures expected for an initial upload.
Build-Depends names only packages that exist (python3-uv-build 0.9.17+ds1-7, pybuild-plugin-pyproject 7.20261030, debhelper-compat 14), and debian/upstream/metadata matches the Homepage/Vcs fields.
uscan found the packaged version as the newest upstream release (upstream 0.4.1, packaged 0.4.1).

Not confirmed ◂

pyproject.toml requires uv_build>=0.9.26,<0.10.0 while the archive's python3-uv-build is 0.9.17+ds1-7. pybuild's PEP 517 build uses --skip-dependency-check, so the constraint is not enforced and the maintainer's build may well have succeeded; whether uv_build 0.9.17 accepts this pyproject (license = "MIT", license-files = ["LICENSE"]) can only be shown by a build. [INFERENCE]
The four PNG screenshots were judged by path and documentation only; their pixel content was not inspected.

Proposed changes ◂

None.

Uploader's response to the LLM review

The uploader was emailed about the review 0 hours ago.

Back to Dashboard | View all reviews for this package