On Mon, Apr 28, 2008 at 08:04:44PM -0500, Manoj Srivastava wrote: > Hi, > On Mon, 28 Apr 2008 19:02:55 +0200, Kurt Roeckx <[EMAIL PROTECTED]> said: > > > dpkg has added new fields in the .dsc and .changes file. > > > They both can now contains two new fields: Checksums-Sha1 > > Checksums-Sha256 > > > 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.
Various other software, like debsign and dak, had to be changed. The policy is not just about what the general package maintainer should know, it's also how our tools should interact. If you don't think the format of the .dsc and .changes should be mentioned in the policy, I suggest you also remove the current one. dpkg-source(1) has minimal documentation about the different source versions, but doesn't seem to mention anything about the format of the .dsc or .changes file. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
