#22883 - Trustable "guix pull" - GNU bug report logs

Package	Source(s)		Maintainer(s)
guix		PTS Buildd Popcon

Message #79 received at 22883@debbugs.gnu.org (full text, mbox, reply):

Received: (at 22883) by debbugs.gnu.org; 5 Jun 2016 21:15:21 +0000
From debbugs-submit-bounces@debbugs.gnu.org Sun Jun 05 17:15:20 2016
Received: from localhost ([127.0.0.1]:55934 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces@debbugs.gnu.org>)
	id 1b9fOC-0008NP-Nj
	for submit@debbugs.gnu.org; Sun, 05 Jun 2016 17:15:20 -0400
Received: from out2-smtp.messagingengine.com ([66.111.4.26]:52556)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <leo@famulari.name>) id 1b9fOB-0008NH-AX
 for 22883@debbugs.gnu.org; Sun, 05 Jun 2016 17:15:19 -0400
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45])
 by mailout.nyi.internal (Postfix) with ESMTP id E003820A89;
 Sun,  5 Jun 2016 17:15:18 -0400 (EDT)
Received: from frontend2 ([10.202.2.161])
 by compute5.internal (MEProxy); Sun, 05 Jun 2016 17:15:18 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=famulari.name; h=
 cc:content-type:date:from:in-reply-to:message-id:mime-version
 :references:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=0U2XI
 KgHN4JLTNVPrnJmlI0GxLA=; b=FU5gPLa06DAo8bCgl0cCwfRkUCKEnWWfoo6dY
 viBHGv7xtZQAA3zn9yeAmh2kD89otG5w3yDFfRPKnbv0pYIBkjZtN1OvQaLHSe07
 Hyi5iEaBFNBubv4F6DF1I+k/WQ/KRWYTMWKNiUh1DhF2qaJfcQFyZ1fX5f4fv+vG
 vL7aio=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-type:date:from:in-reply-to
 :message-id:mime-version:references:subject:to:x-sasl-enc
 :x-sasl-enc; s=smtpout; bh=0U2XIKgHN4JLTNVPrnJmlI0GxLA=; b=oWubl
 D7oRUzHiEmnVbWe+MuCpDEhZ2dCL2TneIfrVLl87T6wPKT1YLDy46jaTSfsKU9zj
 d+4oCqv88UCrwXetyMF2Jfc2JNDa+uJkrIAIl3hG7BQVEMmJEjofvTbK1jkQv0im
 DQ/r3+i5Cactql27EReFkAM6sRE8teu7xyP+pc=
X-Sasl-enc: BoBz/KYYHeMSPbIOwwTmbEj5iVRS08iO7mG9P+aUrtO1 1465161318
Received: from localhost (c-68-81-58-201.hsd1.pa.comcast.net [68.81.58.201])
 by mail.messagingengine.com (Postfix) with ESMTPA id 67D59CCD99;
 Sun,  5 Jun 2016 17:15:18 -0400 (EDT)
Date: Sun, 5 Jun 2016 17:15:17 -0400
From: Leo Famulari <leo@famulari.name>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Subject: Re: Authenticating a Git checkout
Message-ID: <20160605211517.GA2928@jasmine>
References: <87io14sqoa.fsf@dustycloud.org> <87h9ep8gxk.fsf@gnu.org>
 <20160426001359.GA23088@jasmine> <874majg0z8.fsf@gnu.org>
 <87bn3iz1xc.fsf_-_@gnu.org> <87bn3hwpgo.fsf@gnu.org>
 <87wpm519um.fsf@gnu.org> <87h9d7e5g7.fsf@dustycloud.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87h9d7e5g7.fsf@dustycloud.org>
User-Agent: Mutt/1.6.0 (2016-04-01)
X-Spam-Score: -0.7 (/)
X-Debbugs-Envelope-To: 22883
Cc: 22883@debbugs.gnu.org, Mike Gerwitz <mtg@gnu.org>,
 Ludovic Courtès <ludo@gnu.org>
X-BeenThere: debbugs-submit@debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request@debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit@debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request@debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request@debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces@debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
X-Spam-Score: -0.7 (/)

On Sun, Jun 05, 2016 at 03:39:04PM -0500, Christopher Allan Webber wrote:
> One theoretical optimization: if I verify the DAG, could I store
> somewhere that I've verified from commit cabba6e and upward already, so
> the next time I verify it only has to verify the new commits?

AIUI `git verify-commit` takes a single commit as an argument, so you
can pass it an argument like this:

$ git verify-commit $(git rev-list deadbeef..cabba6e)

... and it will only look at those. So, you would tailor the range of
commits that you want to verify.

> Mostly makes sense if we're already going down the only mildly
> crazypants direction of implementing our own tooling :)

It seems you'd want a tool that you trust to store a reference to the
latest commit you trust, and use it to create the range of commits you
pass to `git rev-list`.

Display info messages

Send a report that this bug log contains spam.

debbugs.gnu.org maintainers <help-debbugs@gnu.org>. Last modified: Sun Dec 22 01:37:05 2024; Machine Name: wallace-server

GNU bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

#22883 Trustable "guix pull"