On Tue, Apr 14, 2026 at 09:05:55AM +0900, yokota wrote: > The RC bug was fixed by > https://salsa.debian.org/python-team/packages/python-backports.zstd/-/merge_requests/1 > . > > Please upload new package to Debian if it seems well. > https://salsa.debian.org/python-team/packages/python-backports.zstd
Thanks. Most of this looks OK. I can't understand why https://salsa.debian.org/python-team/packages/python-backports.zstd/-/commit/0da5ed3fad67ba97fd8c881c6c61c0b722f58fd6 makes sense, though. The linked bug isn't saying that _all_ Python packages must build-depend on python3-setuptools-scm; it's only saying that those packages that use setuptools_scm in their upstream build system must do so. This package does not use setuptools_scm. So what's the point of this extra build-dependency? I ran builds both with and without it and it makes no difference to the resulting package, although including the build-dependency does cause this new warning: toml section missing PosixPath('pyproject.toml') does not contain a tool.setuptools_scm section If you fix this, please do it in such a way that you can do a normal git push, not a force-push. I noticed previously that you were force-pushing to this branch quite a lot; that's OK in your own work-in-progress branch that's the source of a merge proposal, but I don't think we should be doing it to primary packaging branches that other developers are likely to have checked out. Thanks, -- Colin Watson (he/him) [[email protected]]
