From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id E9CCE1384B4 for ; Sun, 13 Dec 2015 21:30:48 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D44F021C0B9; Sun, 13 Dec 2015 21:30:30 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id DB32221C002 for ; Sun, 13 Dec 2015 21:30:29 +0000 (UTC) Received: from mail-ig0-f178.google.com (mail-ig0-f178.google.com [209.85.213.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: floppym) by smtp.gentoo.org (Postfix) with ESMTPSA id 9F2CA340836 for ; Sun, 13 Dec 2015 21:30:28 +0000 (UTC) Received: by mail-ig0-f178.google.com with SMTP id mv3so70520543igc.0 for ; Sun, 13 Dec 2015 13:30:28 -0800 (PST) X-Received: by 10.50.111.8 with SMTP id ie8mr15428816igb.65.1450042226319; Sun, 13 Dec 2015 13:30:26 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Received: by 10.107.3.27 with HTTP; Sun, 13 Dec 2015 13:30:06 -0800 (PST) In-Reply-To: <20151213222001.0c1c466a3f3b8b0b53c69a9d@gentoo.org> References: <566DACB3.2010105@gentoo.org> <20151213222001.0c1c466a3f3b8b0b53c69a9d@gentoo.org> From: Mike Gilbert Date: Sun, 13 Dec 2015 16:30:06 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [gentoo-dev] repo/gentoo.git, or how committing is challenging To: Gentoo Dev Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: b6cce5a5-2928-48f1-ba6a-ae94dd0f7670 X-Archives-Hash: 7a2322c7b25e8cc168058ed0cdc9a3c9 On Sun, Dec 13, 2015 at 2:20 PM, Andrew Savchenko wrote: >> Since signing is mandatory since the git migration, ahem, this means >> that no one in the last 5 months(!) actually followed the documentation >> (because that does NOT work!). I'm almost impressed, but, wow, this is >> enterprisey. > > It is absolutely possible to create correct gpg key, put it into > LDAP according to GLEP and to sign commits and pushes properly. If gkeys is as broken as Patrick describes, it might be helpful to have step-by-step instructions for manually generating an appropriate key. This would help new developers.