From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id D26D0138334 for ; Fri, 6 Jul 2018 20:32:02 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9B5F7E09CD; Fri, 6 Jul 2018 20:31:54 +0000 (UTC) Received: from mail-pl0-f47.google.com (mail-pl0-f47.google.com [209.85.160.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id F02A9E09BD for ; Fri, 6 Jul 2018 20:31:53 +0000 (UTC) Received: by mail-pl0-f47.google.com with SMTP id t6-v6so3345640plo.7 for ; Fri, 06 Jul 2018 13:31:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=YtYzqh6ttvO0erodijGlTnMMdixvK9q7j9c5IIrBruY=; b=HaF+11jING4rXOQCPnwvcoR9bb/N/Z8EF56Yn14Iosr9QjlYOl+s/rdLEA90XPfKAN qDSebdzlkU0Av+ow+Ug3iVxqqI8goeZZaL3y7VgiptPw8StmJ1R+yZeutXOc+hBvPAxs Y3mze8NEz9v+60DX/j9T5sPcck8XRRKfJmpMzVmODWPkMghFeYl4MFq0CfNfpjcubwuT ZnT20e0pATrwMXjXMZMiJkudI6WtCnKUIPHh/be8+EuiKe2DCbK8ET4nwdWk/UkxfME9 qaOzaq0zHiiQVlDUw10B1vdLFtl+XurA9W4GeKuH6MO/ZYwJUsx+JZRGfCja5R0Ayv1D K/Bg== X-Gm-Message-State: APt69E3YQ9Y++S4/+vYdY+2dAqTG4yGTM9YH8NyyptqhKicP4wKn10uz 17jnJcSOO0RYDHFC+D/LKL4TvEx85Hq0FxVf/NWdww== X-Google-Smtp-Source: AAOMgpd8SNShdbOfNWIVsXJnUMo3+Ak3VqThsgbOt6LbnemxfW9KJbAQGGDQjC7T+2BKas8949eBZkog1kartRrzIb8= X-Received: by 2002:a17:902:8b86:: with SMTP id ay6-v6mr11626533plb.295.1530909112519; Fri, 06 Jul 2018 13:31:52 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 References: In-Reply-To: From: Rich Freeman Date: Fri, 6 Jul 2018 16:31:41 -0400 Message-ID: Subject: Re: [gentoo-user] How long does "Verifying /usr/portage" take? To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 7da7f8c5-4280-4386-a65e-608b615de6e5 X-Archives-Hash: 40e39e260e0eb445dc471cf47b6fae17 On Fri, Jul 6, 2018 at 3:02 PM Grant Edwards wrote: > > Now that the public key stuff is working again (knock on wood), I'm > curious if it's usual for an emerge --sync to take 10-15 minutes > longer than it used due to the "Verifying /usr/portage" step. > Again, the sync mechanisms are different, but I note that the git verify is nearly instant. Of course, the only thing being fed to gpg in the git case is the git commit record itself, which is about 10 lines of text. That record contains a content hash of the tree record, which in turn references content hashes of every directory inside, and so on. So, with git most of the hash validation is happening constantly just by virtue of everything being content-hashed, and the only extra layer with the gpg signature is to sign the top level of the whole tree. Now, on the flip side, some of those git operations might take time since it is stating files for things like git status/etc. I've never noticed an issue, but I'm also on an SSD and tend to always have a warm cache when I'm using it. emerge shouldn't need to trigger any git operations except when syncing. -- Rich -- Rich