From owner-cvs-all@FreeBSD.ORG Mon Jan 23 09:52:23 2006 Return-Path: X-Original-To: cvs-all@FreeBSD.org Delivered-To: cvs-all@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A487C16A41F; Mon, 23 Jan 2006 09:52:23 +0000 (GMT) (envelope-from edwin@mavetju.org) Received: from mail2out.barnet.com.au (mail2out.barnet.com.au [202.83.176.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE70543D58; Mon, 23 Jan 2006 09:52:22 +0000 (GMT) (envelope-from edwin@mavetju.org) Received: by mail2out.barnet.com.au (Postfix, from userid 27) id C44647073EA; Mon, 23 Jan 2006 20:52:20 +1100 (EST) X-Viruscan-Id: <43D4A7540000F931DE4524@BarNet> Received: from mail2-auth.barnet.com.au (mail2.barnet.com.au [202.83.176.13]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.barnet.com.au", Issuer "BarNet Root Certificate Authority" (verified OK)) by mail2.barnet.com.au (Postfix) with ESMTP id 828CC7073E4; Mon, 23 Jan 2006 20:52:20 +1100 (EST) Received: from k7.mavetju (edwin-3.int.barnet.com.au [10.10.12.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail2-auth.barnet.com.au (Postfix) with ESMTP id A5D827073E3; Mon, 23 Jan 2006 20:52:19 +1100 (EST) Received: by k7.mavetju (Postfix, from userid 1001) id E2C731DF; Mon, 23 Jan 2006 20:52:13 +1100 (EST) Date: Mon, 23 Jan 2006 20:52:13 +1100 From: Edwin Groothuis To: Darren Pilgrim Message-ID: <20060123095213.GV1020@k7.mavetju> References: <200601222124.k0MLO5A9083860@repoman.freebsd.org> <000001c61faf$30bcdf60$672a15ac@smiley> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000001c61faf$30bcdf60$672a15ac@smiley> User-Agent: Mutt/1.4.2.1i Cc: cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: "SHA256ify" commits X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2006 09:52:23 -0000 On Sun, Jan 22, 2006 at 03:54:30PM -0800, Darren Pilgrim wrote: > There's no criticism here, just one geek's interested query. I'm already > familiar with the reasons for moving to SHA256, but how is this process > being accomplished? What are you using to calculate and insert the new > hashes? What conditions result in the "manually checked and updated" > commit? If there's previous list traffic answering these questions, by all > means, point me in a direction. The way it's done right now is best described as "blunt axe": - Run "make checksun", which downloads the files and checks them for validity. - Run "make makesum", which adds the SHA256 lines - Diff the old distinfo and new distinfo for lost lines. - If no lost lines, commit. The commit info only shows +n and -0. The "manually checked and updated" ones are ones on which the diff showed -n (where n!=0) and checked for validity, for example the relocation of SIZE or extra files which the normal "mkae checksum" didn't fetch. Of course I'm going to miss one or two lines, but a distinfo parser will later on tell me what I'm still missing. Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://weblog.barnet.com.au/edwin/