Package: perltidy
Version: 20220613-1
Severity: normal
Hi Don,
I notice that upstream has released 20221112 (prompted by the fact that upstream
openqa has a versioned depends on that new version)
I knocked up a new version of the package, which is visible here:
https://salsa.debian.org/philh/perltidy
but which provokes lintian to say that there are sources missing:
https://philh.pages.debian.net/-/perltidy/-/jobs/3847974/artifacts/debian/output/lintian.html
which seems to be because the pod files under ./local-docs/ in the upstream git
repo don't make it into the tarballs.
I guess one could put them back in, or start basing the package on the git tags
instead of the tarballs -- that seems like a decission for the maintaner, so
I'll leave it up to you.
Regarding tags: I note that they have also used tags of the form 20221112.03
which presumably either mean point releases of 20221112 or pre-releases of the
next actual release, but I'm not sure which, or whether that should be
considered a version to package.
HTH
Cheers, Phil.
