Re: Include git commit id and git tree id in *.changes files when uploading?
Hi!
> > Has somebody else already been thinking about the same? Do others see
> > value in this?
>
> tag2upload and dgit already do this.
>
> for example:
>
> $ apt-cache showsrc sasview
> Package: sasview
> Binary: sasview, python3-sasview, sasview-doc
> Version: 6.1.1-1
> [...]
> Dgit: 524114d36f378912d0597e691a1d67c32c9bf01a debian
> archive/debian/6.1.1-1 https://git.dgit.debian.org/sasview
> Git-Tag-Info: tag=64770d6dab76cb04b84188672badc32c5ae2e71b
> fp=90e2d2c1ad146a1b7ebb891dbbc17ebb1396f2f7
> Git-Tag-Tagger: Stuart Prescott <stuart@debian.org>
> [...]
>
> The Dgit field has been documented in policy 3.9.5 in 2013. The two
> tag2upload-related fields (Git-Tag-Info and Git-Tag-Tagger) are #1091868
> which is pending upload.
Thanks Stuart for pointing this out, I wasn't aware. That
"Git-Tag-Info" git object id can be verified as your commit at
https://salsa.debian.org/science-team/sasview/-/commit/64770d6dab76cb04b84188672badc32c5ae2e71b
Are you aware of any attempts to integrate this into dpkg-buildpackage
toolchain so systems that build .deb packages can have that metadata
field universally and not just via official Debian uploads via
tag2upload?
Reply to: