From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37048) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fuZf8-0008E9-II for guix-patches@gnu.org; Tue, 28 Aug 2018 04:47:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fuZVi-0006hq-EI for guix-patches@gnu.org; Tue, 28 Aug 2018 04:38:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:58034) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fuZVi-0006hj-AE for guix-patches@gnu.org; Tue, 28 Aug 2018 04:38:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fuZVh-0007QL-VU for guix-patches@gnu.org; Tue, 28 Aug 2018 04:38:01 -0400 Subject: [bug#32102] [PATCH v2 2/2] gnu: gajim: Combine wrap-program phases. Resent-Message-ID: From: Arun Isaac In-Reply-To: <87mut8avme.fsf@gnu.org> 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: Tue, 28 Aug 2018 14:07:04 +0530 Message-ID: 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 32102@debbugs.gnu.org, =?UTF-8?Q?Cl=C3=A9ment?= Lassieur > Right. I re-read it and it=E2=80=99s all clear again. :-) The issue is= that > =E2=80=98list-of-files=E2=80=99 in the =E2=80=98wrap=E2=80=99 phase of py= thon-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-upd= ates=E2=80=99 > cycle. :-/ So I think it=E2=80=99ll have to be for next time. Sounds g= ood? > > 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?