Bug#478295: Sha1 and sha256 in .changes and .dsc file
From: Manoj Srivastava <firstname.lastname@example.org>
> On Mon, 28 Apr 2008 19:02:55 +0200, Kurt Roeckx <email@example.com> said:
>> dpkg has added new fields in the .dsc and .changes file.
>> They both can now contains two new fields: Checksums-Sha1
>> They act the same as Files, but use sha1 and sha256 instead of md5.
> This is fine, but why does this need to be in policy, as opposed
> to dpkg documentation? As far as I can see, I, as a package
> maintainer, had to do absolutely nothing when this change happened; the
> .dsc and .changes files are normally output files, and not something
> that needs be created by the maintainer.
Policy is the only formal documentation we have right now of the control
fields in a Debian package, so I think there's at least a prima facie
argument for adding a specification for any new fields to Policy, at least
unless that documentation is split off to some other source. I don't know
of any other documentation that covers all the recognized control fields.
Russ Allbery (firstname.lastname@example.org) <http://www.eyrie.org/~eagle/>