On Sun, Jan 15, 2023 at 09:09:05PM +0100, Axel Beckert wrote: > Dear Steve, > Steve Langasek wrote: > > > [1] https://code.ungleich.ch/ungleich-public/cdist/commit/b974969f28f4 > > Well, that's not the upstream repo listed in debian/copyright, > JFTR: > https://salsa.debian.org/debian/cdist/-/blob/debian/7.0.0-1/debian/upstream/metadata > already had the up to date upstream VCS repo at the time you wrote the > bug report. And that's the _canonical_ (sic!) place to look for the > upstream VCS repo. It absolutely is not. Many packages that declare a Vcs URI in debian/control don't provide upstream branches at all; those that do, do not generally have any jobs in place to automatically sync from upstream; and it's the nature of git that in the absence of looking at the content of such a job, you do not know where the actual upstream is or whether the branch is up to date with respect to it. The only standard way to declare a pointer to upstream is in debian/copyright, and that pointer pointed at a repo that had not been updated. Y'all are free to do what you want with this package, but it's in no way my obligation to go hunting around for upstream git repos declared elsewhere. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slangasek@ubuntu.com vorlon@debian.org
Attachment:
signature.asc
Description: PGP signature