Only 1.4.0-r1 and 1.4.1 has the compability patch for alternative machine-id file location: ibus-1.4.0-r1.ebuild: "${FILESDIR}"/${P}-machine-id-fallback.patch ibus-1.4.1.ebuild: "${FILESDIR}"/${PN}-1.4.0-machine-id-fallback.patch And now dbus-1.4.18 is going stable from bug 403843 I'm not familiar with ibus otherwise so leaving it to maintainers to CC arch's
OK, pretty much exhausted every possible contact channel for the CJK guys (mailing list, cjk@g.o mail, mailing list) and seems to be pretty impossible to get anyone intrested So CCing arches, lets hope this won't break much
(In reply to comment #1) > OK, pretty much exhausted every possible contact channel for the CJK guys > (mailing list, cjk@g.o mail, mailing list) and seems to be pretty impossible > to get anyone intrested typo, should say 'direct mails to developers' instead of 'mailing list' again. sorry.
ppc64 done
ppc done
Hi, sorry for long silence. cjk herd back. I'm taking look at these ibus related bugs to find out if there's serious bugs to prevent stabilization. I'm taking look at these ibus related bugs to find out if there're serious bugs to prevent stabilization. #294883 app-i18n/ibus-chewing fails to build #342141 app-i18n/ibus: keys won't work with app-office/gnucash #364055 app-18n/ibus-table-1.3.0.20100621 - install included tables #366045 app-i18n/ibus-pinyin-1.3.99.20101029 conflict type definition #386535 Cannot build app-i18n/ibus-table-cantonese 1.2.0.20100305 #388735 app-i18n/ibus: python flag badly used #390009 app-i18n/ibus-table should depend on needed USE flags instead of dying #390327 app-i18n/ibus-table-xingma fails to build with the latest app-i18n/ibus-table #395239 app-i18n/ibus-1.4.0: failed at autoconf if no gconf installed. #402397 app-i18n/ibus-mozc-1.3.975.102 with app-i18n/ibus-1.4.1 - unix/ibus/mozc_engine.cc:623:56: error: ‘struct IBusP
(In reply to comment #5) > Hi, sorry for long silence. cjk herd back. > > I'm taking look at these ibus related bugs to find out if there's > serious bugs to prevent stabilization. I'm not sure what you are trying to say with listing these bugs. Are any of them serious regressions? As you can find out from Comment #0, this is stabilization *really required*. Alternative is reverting ibus and all of it's reverse dependencies back to ~arch only (and removing everything below 1.4.0-r1)
(In reply to comment #6) > (In reply to comment #5) > > Hi, sorry for long silence. cjk herd back. > > > > I'm taking look at these ibus related bugs to find out if there's > > serious bugs to prevent stabilization. > > I'm not sure what you are trying to say with listing these bugs. Are any of > them serious regressions? I just want to show I'm working on this bug since you called cjk herd on the ML. > As you can find out from Comment #0, this is stabilization *really > required*. > Alternative is reverting ibus and all of it's reverse dependencies back to > ~arch only (and removing everything below 1.4.0-r1) hm, I feel I got lost :S As you called cjk on the list, I've tried to look around this, but ... actually what's needed? To be honest, I don't understand why you called cjk on this. Yeah, it was better for me to ask this simple question instead of finding out possible serious bugs: "Hi, cjk here. Could you tell me what you want me to do here?"
nevermind, just wanted to know if there are known blockers for stabilizing ibus. lets move on here :) (sorry for confusion or whatever :)
amd64/x86 stable
