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 A14F71381F3 for ; Thu, 20 Jun 2013 09:21:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 58CF8E0A7E; Thu, 20 Jun 2013 09:21:21 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 79EBAE0A41 for ; Thu, 20 Jun 2013 09:21:20 +0000 (UTC) Received: from localhost (213-238-104-114.adsl.inetia.pl [213.238.104.114]) (using SSLv3 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 83D4D33E47C; Thu, 20 Jun 2013 09:21:18 +0000 (UTC) Date: Thu, 20 Jun 2013 11:16:46 +0200 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: gentoo-dev@lists.gentoo.org Cc: phajdan.jr@gentoo.org Subject: Re: [gentoo-dev] repoman commit unexpectedly drops FEATURES="sign" on error Message-ID: <20130620111646.4ecb37d4@gentoo.org> In-Reply-To: <51C26FFC.1090000@gentoo.org> References: <51C26FFC.1090000@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.9.1 (GTK+ 2.24.19; x86_64-pc-linux-gnu) 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 Content-Type: multipart/signed; micalg=PGP-SHA512; boundary="Sig_/KM9TISZ6C9vMP/65e2nhC9T"; protocol="application/pgp-signature" X-Archives-Salt: 0995e8d5-05ea-4243-9c21-cacf724a2079 X-Archives-Hash: 5394fd79a20951c40cbd7065281453f1 --Sig_/KM9TISZ6C9vMP/65e2nhC9T Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dnia 2013-06-19, o godz. 19:59:08 ""Pawe=C5=82 Hajdan, Jr."" napisa=C5=82(a): > I was surprised by repoman just dropping FEATURES=3D"sign" . I'm aware > that at that time it has to commit an updated Manifest to prevent > breakages, so if gpg fails it proceeds, but is there something it could > do to check gpg sanity before committing anything? I'm pretty sure this was discussed already, either here or on bugzie. Doing test signatures won't cover all failures. IMHO the best thing to do would be to drop CVS keywords and let repoman do normal commits instead of this two-step thing. But some of the devs really prefer to keep them, at least until we migrate to git and have better ways of e.g. checking the file version. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/KM9TISZ6C9vMP/65e2nhC9T Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iQJ8BAEBCgBmBQJRwsiBXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ1RUJGMjBGOTk2RkIzQzIyQ0M2RkNBNDBC QUJGMUQ1RkY4QzgxMTBBAAoJELq/HV/4yBEKI8oQAKf6mvOR/iJH+KQ8YrXaOCdh vXF8fKk6HI3j0VO/eoDXyf2xBXgXiVOSFav5UhDS+6zGj4F9bjRNULrEnJXwTXIO 4bYFh9/TMDem83S4dKsF3Is2+HUxkgVsUmzkJ69p3PVQxbLROwIHIjYqKaraJqUG i8P8ctxhTC8Fq5DOAO6Tr7u+H94Ex6MhbILm44mZ3hIn6P8vT7Mg16MkdaPCFWPJ cDl2LtRo7own6WlUzbMWxQWRwfgpLVck2vH6fyaR1azf5XW29BhuAGBUWr5NGJgC JECC/zj7SVyBi1TWnyQPNjGSf88CK8M8ZFyEtIN3UHLnNa9X73d5zqX39mdjlbLE ubXzOaePB6OVNgW8bXg68gJfoHRpfiDD8Z+rTCmgg6hNYL+xT/hxjH5TZ3aWQpbI sL7QfKC5pRCr3FsKL0cml/HRlmdgLOTCVJsMx8dVtOFkwA+sAt0XC+iAV1CJPmsP MntYUy06wkPShhXp/slip+9sGa3cA9Rfs48Qr/OOG5j1hw5voKU7Eh23jZrg+GFM Q9WnsFlLilQ2Y5VxCxu1DZIMKy1hSpcfLxgYJw9u22yXkdMs1iWuZKhNdbLimGoW I5bqB315WR8RnQ0VBkQDgKpQpsJF9XFfaO56dKerfk+Jn8ISGujTdV7kgRMW2Aij RDtS8PrMng8ln81oHzn6 =5zHT -----END PGP SIGNATURE----- --Sig_/KM9TISZ6C9vMP/65e2nhC9T--