Your message dated Mon, 28 Apr 2008 20:04:44 -0500 with message-id <87iqy1cvyr.fsf@anzu.internal.golden-gryphon.com> and subject line Re: Bug#478295: Sha1 and sha256 in .changes and .dsc file has caused the Debian Bug report #478295, regarding Sha1 and sha256 in .changes and .dsc file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 478295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478295 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Sha1 and sha256 in .changes and .dsc file
- From: Kurt Roeckx <kurt@roeckx.be>
- Date: Mon, 28 Apr 2008 19:02:55 +0200
- Message-id: <[🔎] 20080428170255.GA26117@roeckx.be>
Package: debian-policy Version: 3.7.3.0 Hi, 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. Kurt
--- End Message ---
--- Begin Message ---
- To: Kurt Roeckx <kurt@roeckx.be>
- Cc: 478295-done@bugs.debian.org
- Subject: Re: Bug#478295: Sha1 and sha256 in .changes and .dsc file
- From: Manoj Srivastava <srivasta@debian.org>
- Date: Mon, 28 Apr 2008 20:04:44 -0500
- Message-id: <87iqy1cvyr.fsf@anzu.internal.golden-gryphon.com>
- In-reply-to: <[🔎] 20080428170255.GA26117@roeckx.be> (Kurt Roeckx's message of "Mon, 28 Apr 2008 19:02:55 +0200")
- References: <[🔎] 20080428170255.GA26117@roeckx.be>
Hi, On Mon, 28 Apr 2008 19:02:55 +0200, Kurt Roeckx <kurt@roeckx.be> 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. manoj -- Per buck you get more computing action with the small computer. R.W. Hamming Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/~srivasta/> 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--- End Message ---