From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:39459) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fv7It-0000EJ-2S for guix-patches@gnu.org; Wed, 29 Aug 2018 16:43:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fv7Is-0003Cr-6z for guix-patches@gnu.org; Wed, 29 Aug 2018 16:43:02 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:60696) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fv7Is-0003Ck-2T for guix-patches@gnu.org; Wed, 29 Aug 2018 16:43:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fv7Ir-0002bZ-Vl for guix-patches@gnu.org; Wed, 29 Aug 2018 16:43:02 -0400 Subject: [bug#32102] [PATCH v2 2/2] gnu: gajim: Combine wrap-program phases. Resent-Message-ID: From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) References: <20180711192652.20186-1-arunisaac@systemreboot.net> <20180711192652.20186-3-arunisaac@systemreboot.net> <87zhyv1qe8.fsf@lassieur.org> <87y3dudsz0.fsf@gnu.org> <87mut8avme.fsf@gnu.org> Date: Wed, 29 Aug 2018 22:42:29 +0200 In-Reply-To: (Arun Isaac's message of "Tue, 28 Aug 2018 14:07:04 +0530") Message-ID: <87wos89a6i.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Arun Isaac Cc: 32102@debbugs.gnu.org, =?UTF-8?Q?Cl=C3=A9ment?= Lassieur Arun Isaac skribis: >> Right. I re-read it and it=E2=80=99s all clear again. :-) The issue i= s that >> =E2=80=98list-of-files=E2=80=99 in the =E2=80=98wrap=E2=80=99 phase of p= ython-build-system would pick up >> files that are themselves wrappers already. >> >> Because of my slow reaction we missed the train of this =E2=80=98core-up= dates=E2=80=99 >> cycle. :-/ So I think it=E2=80=99ll have to be for next time. Sounds = good? >> >> Let=E2=80=99s not forget about it=E2=80=A6 > > Sure, no problem! Sounds good. Apart from closely following the > guix-devel list, is there anyway I can know when the next core-updates > cycle comes up? Not really, it=E2=80=99s rather informal, so you have to pay attention to heads-up messages on guix-devel and to branch creations/deletions on guix-commits. Ludo=E2=80=99.