=app-i18n/mozc-1.10.1390.102 hard depend on =dev-libs/protobuf-2.4.1, so there is conflicts with chromium, since it pull in =devlibs/protobuf-2.5.0 I removed this hard-coded dependency, and mozc-1.10 still build fine, is there someone can verify it still works (run time check)? with =dev-libs/protobuf-2.5.0 thanks These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild UD ] dev-libs/protobuf-2.4.1 [2.5.0] [ebuild R ] app-i18n/mozc-1.10.1390.102 [1.10.1390.102] !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: dev-libs/protobuf:0 (dev-libs/protobuf-2.5.0::gentoo, installed) pulled in by dev-libs/protobuf:0/8= required by (www-client/chromium-29.0.1547.22::gentoo, installed) (dev-libs/protobuf-2.4.1::gentoo, ebuild scheduled for merge) pulled in by ~dev-libs/protobuf-2.4.1 required by (app-i18n/mozc-1.10.1390.102::gentoo, ebuild scheduled for merge) It may be possible to solve this problem by using package.mask to prevent one of those packages from being selected. However, it is also possible that conflicting dependencies exist such that they are impossible to satisfy simultaneously. If such a conflict exists in the dependencies of two different packages, then those packages can not be installed simultaneously. You may want to try a larger value of the --backtrack option, such as --backtrack=30, in order to see if that will solve this conflict automatically. For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. Reproducible: Always
Created attachment 354148 [details, diff] fix the ebuild deps
(In reply to Dennis 'dlan' Lan from comment #1) > Created attachment 354148 [details, diff] [details, diff] > fix the ebuild deps hi @naota, I think this is just a typo? which commited by accident also do you plan to bump mozc to version 1.11.x? (also it enter maintenance mode) https://code.google.com/p/mozc/issues/detail?id=194
(In reply to Dennis 'dlan' Lan from comment #2) > (In reply to Dennis 'dlan' Lan from comment #1) > > Created attachment 354148 [details, diff] [details, diff] [details, diff] > > fix the ebuild deps > > hi @naota, I think this is just a typo? which commited by accident The dep is completely added by accident. I was trying to unbundle protobuf, but failed. > also do you plan to bump mozc to version 1.11.x? (also it enter maintenance > mode) > > https://code.google.com/p/mozc/issues/detail?id=194 Please fill a bug for the bump.
*** Bug 471286 has been marked as a duplicate of this bug. ***
This issue might be unresolved for the current latest mozc 2.16.2037.102. I had problems emerging =app-i18n/mozc-2.16.2037.102 with =dev-libs/protobuf-2.5.0-r2 but after unmasking =dev-libs/protobuf-2.6.1-r3 it emerged just fine. I apologize for not including proper bug reports, as the incident happened last night and was not recorded. For what it's worth, I had a separate protobuf 2.6 installation in /usr/local while 2.5 was installed as a Gentoo package. This may have caused the issue, but after removing the 2.6 install, and attemping emerge again, the problem persisted. Then, only after unmasking/upgrading to protobuf-2.6.1-r3 through portage did the mozc emerge properly.