From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/2] Fix IBus input methods.
Date: Sat, 03 Sep 2016 15:54:47 +0200 [thread overview]
Message-ID: <87y439ks0o.fsf@gnu.org> (raw)
In-Reply-To: <idjtwdygz9v.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Fri, 2 Sep 2016 16:19:24 +0200")
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.
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?
Thanks in advance! :-)
Ludo’.
next prev parent reply other threads:[~2016-09-03 13:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 22:09 [PATCH 0/2] Fix IBus input methods Ricardo Wurmus
2016-08-24 22:09 ` [PATCH 1/2] gnu: gtk+-2: Add patch to support GUIX_GTK2_IM_MODULE_FILE Ricardo Wurmus
2016-08-24 22:09 ` [PATCH 2/2] gnu: gtk+: Add patch to support GUIX_GTK3_IM_MODULE_FILE Ricardo Wurmus
2016-08-25 9:15 ` [PATCH 0/2] Fix IBus input methods Ricardo Wurmus
2016-08-25 11:06 ` 宋文武
2016-08-25 11:52 ` Ricardo Wurmus
2016-09-02 13:15 ` Ludovic Courtès
2016-09-02 14:19 ` Ricardo Wurmus
2016-09-03 13:54 ` Ludovic Courtès [this message]
2016-09-04 6:42 ` Ricardo Wurmus
2016-11-18 10:37 ` Chris Marusich
2016-11-18 21:28 ` Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y439ks0o.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).