From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ricardo Wurmus <rekado@elephly.net>
Subject: Re: [PATCH 0/2] Fix IBus input methods.
Date: Sun, 04 Sep 2016 08:42:08 +0200
Message-ID: <874m5w9nen.fsf@elephly.net>
References: <20160824220937.8745-1-rekado@elephly.net>
	<87k2f5cdkz.fsf@member.fsf.org> <87zio1njzj.fsf@elephly.net>
	<87inuejvdr.fsf@gnu.org>
	<idjtwdygz9v.fsf@bimsb-sys02.mdc-berlin.net>
	<87y439ks0o.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:45131)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rekado@elephly.net>) id 1bgR8L-00005g-6U
	for guix-devel@gnu.org; Sun, 04 Sep 2016 02:42:26 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rekado@elephly.net>) id 1bgR8J-00069n-3x
	for guix-devel@gnu.org; Sun, 04 Sep 2016 02:42:24 -0400
In-reply-to: <87y439ks0o.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Ludovic =?utf-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: guix-devel@gnu.org


Ludovic Courtès <ludo@gnu.org> writes:

> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> Ricardo Wurmus <rekado@elephly.net> skribis:
>>>
>>>> 宋文武 <iyzsong@member.fsf.org> writes:
>>>>
>>>>> Ricardo Wurmus <rekado@elephly.net> writes:
>>>>>
>>>>>>   gnu: gtk+-2: Add patch to support GUIX_GTK2_IM_MODULE_FILE.
>>>>>>   gnu: gtk+: Add patch to support GUIX_GTK3_IM_MODULE_FILE.
>>>>>
>>>>> Look good to me!
>>>>
>>>> Thanks!
>>>>
>>>> What do you think: should this be a separate branch (e.g. “gtk-rebuild”)
>>>> or should it be pushed to “core-updates”?
>>>
>>> As discussed on IRC, I’ve added a “jobset”:
>>>
>>>   https://hydra.gnu.org/jobset/gnu/gtk-im-modules
>>>
>>> There seems to be only 1 new failure compared to ‘master’:
>>>
>>>   https://hydra.gnu.org/eval/109124?compare=master#tabs-now-fail
>>>
>>> Could you take a look?
>>
>> This looks unrelated to me.
>
> OK.
>
>>> We’ll have to merge ‘master’ into it and evaluate it again.
>>
>> Can “gtk-im-modules” not be merged into the master branch directly?
>
> One benefit of having a separate jobset is that we can wait until
> everything is built before merging to master.  The problem here is that
> this branch was entirely built several days ago, so it might be somewhat
> outdated now.

I understand.

> Thus, could you either (1) merge locally into master and make sure no
> important binaries are missing (try “guix build emacs -n” or similar),
> and if that is the case, you can push; or (2) merge master into
> gtk-im-modules and reevaluate the jobset?

I tried with “emacs”, “icecat”, “epiphany”, “ardour”, “gnome-desktop”,
“libgnomeui”, and “libxfce4ui” — all of them only report that they would
download substitutes.  None report that anything would need to be built
locally.

So, I’ll go ahead and merge “gtk-im-modules” into “master” and push to
master in a few minutes.

~~ Ricardo