From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: =?utf-8?Q?=E2=80=98core-updates=E2=80=99?= merge is a squashed commit Date: Thu, 04 Aug 2016 16:07:29 +0200 Message-ID: <874m70wrtq.fsf@gnu.org> References: <871t253ith.fsf@gnu.org> <20160803172417.GA10236@jasmine> <878twd20ui.fsf@gnu.org> <20160803183911.GC11621@jasmine> <87wpjxy4ta.fsf_-_@gnu.org> <20160803211032.GA6034@jasmine> <87a8gtyntw.fsf@netris.org> <20160804082400.GA1638@solar> <87ziosyalv.fsf@netris.org> <20160804124032.GA5789@solar> <20160804130409.GB6326@jasmine> <87vazgy8ex.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42387) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bVJJD-0000EU-TG for guix-devel@gnu.org; Thu, 04 Aug 2016 10:07:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bVJJ8-0007B3-Ag for guix-devel@gnu.org; Thu, 04 Aug 2016 10:07:38 -0400 In-Reply-To: <87vazgy8ex.fsf@netris.org> (Mark H. Weaver's message of "Thu, 04 Aug 2016 09:23:50 -0400") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Mark H Weaver Cc: guix-devel@gnu.org Mark H Weaver skribis: > Leo Famulari writes: > >> On Thu, Aug 04, 2016 at 02:40:32PM +0200, Andreas Enge wrote: >>> On Thu, Aug 04, 2016 at 08:36:28AM -0400, Mark H Weaver wrote: >>> Good news, thanks for all this work! >> >> Indeed! >> >>> > Unfortunately, when I tried to push it to 'master', it was rejected >>> > because of 56 unsigned commits on the 'core-updates' branch. Note th= at >>> > all of the new commits I made (the reverts, the merge, and the >>> > cherry-picks) were all signed by me. The unsigned commits that are >>> > blocking this have been on the 'core-updates' branch for quite some >>> > time. >>> >=20 >>> > If there are unsigned commits on 'core-updates-next', I guess we'll r= un >>> > into the same problem trying to merge that branch later. >> >> Yes, I had this problem yesterday. >> >>> A possible solution would be to disable the commit hook that forces >>> signatures, make these commits, and reenable the hook; hoping that noone >>> adds an unsigned commit in the meantime... It would require to coordina= te >>> with a savannah administrator. >> >> I think we have to do this, unfortunately. > > I just did this. Huge thanks to Lisa Marie Maginnis, GNU sysadmin > extraordinaire, for promptly responding to my plea for help :) Awesome, thank you all! > However, we should take steps to avoid this problem in the future. The > most recent unsigned commit on 'core-updates' was from only 3 days ago, > by Andreas. "gnu: unison: Add input ghostscript". I'm fairly sure this > was after we added the commit hook, so I guess the hook only applies to > 'master'. > > So, if I understand correctly, we're currently in a state where unsigned > commits can accidentally get pushed to other branches, making those > branches unmergeable into 'master'. The hook can be seen at (search for =E2=80=9CAttached Files=E2=80=9D): https://savannah.gnu.org/support/?109104 I think it should work equally well for all branches. That said, the hook is so simple that it may well be simplistic, so do not hesitate to send improvements to the hook in this Savannah ticket. Thanks! Ludo=E2=80=99.