> > On Wed, Nov 27, 2024 at 01:11:14PM -0800, Otto Kekäläinen wrote: > >> Package: debian-policy > >> Found: 4.7.0.1 > >> > >> I would like to suggest the Debian Policy to recommend a specific > >> Debian package version string scheme in cases where upstream has no > >> releases, but they do have git commit ids to refer to: > > > > I'm not sure if this should be in Policy, but it might make sense to > > document as "best practice" in the devleopers referrence? > > Yes, I was thinking the same. Let's reassign this bug?
Please no. Rather close it and state that you do not accept this in the policy so that there is an audit trail that this was rejected from policy and who made the decision. Updates/changes elsewhere can then refer this bug as a source that there is no policy for version strings of this sorts. Or more people can chime in and request it to be re-opened etc. I assume some of the maintainers of nearly 900 packages currently using this might have an interest to see that the policy was rejected: ± curl http://ftp.debian.org/debian/dists/sid/main/binary-amd64/Packages.xz | unxz > Packages ± zgrep --only-matching -P '/.*0.0~git.*.deb' Packages | wc -l 893
