mysql-query-browser-1.1.18.ebuild has an RDEPEND on dev-cpp/gtkmm-2.8*, but all gtkmm-2.8 are replaced by 2.10 versions for ~amd64 and ~x86 Reproducible: Always Steps to Reproduce: Actual Results: # emerge -uDNva world These are the packages that would be merged, in order: Calculating world dependencies | !!! Multiple versions within a single package slot have been !!! pulled into the dependency graph: ('ebuild', '/', 'dev-cpp/gtkmm-2.8.3', 'merge') pulled in by ('ebuild', '/', 'dev-db/mysql-query-browser-1.1.18', 'nomerge') ('ebuild', '/', 'dev-cpp/gtkmm-2.10.6', 'nomerge') pulled in by ('ebuild', '/', 'dev-cpp/libgnomecanvasmm-2.16.0', 'nomerge') ('ebuild', '/', 'dev-cpp/libglademm-2.6.3', 'nomerge') ('ebuild', '/', 'dev-cpp/libgnomemm-2.16.0', 'nomerge') ('ebuild', '/', 'app-cdr/cdrdao-1.2.2', 'nomerge') ('ebuild', '/', 'dev-cpp/gconfmm-2.16.0', 'nomerge') Expected Results: mysql-query-browser works fine (for my small test) with the new gtkmm. I expect it to emerge the new library and not complain about mysql-query-browser. workaround: sed -i 's#=dev-cpp/gtkmm-2.8#=dev-cpp/gtkmm-2.10#' /usr/portage/dev-db/mysql-query-browser/mysql-query-browser-1.1.18.ebuild ebuild /usr/portage/dev-db/mysql-query-browser/mysql-query-browser-1.1.18.ebuild digest
So use dev-db/mysql-gui-tools; it contains a newer version. TBH, I fails to see why we still have this ebuild in the tree, it should be removed.
good point, I used mysql-query-browser because it emerged without problems, while dev-db/mysql-gui-tools will not. I will add info so mysql-gui-tools-5.0_p9 can be fixed. (could make a new bugrep, but as fixing mysql-gui-tools will make this bug superfluous i will re-use this one)
Created attachment 109574 [details, diff] patch on mysql-gui-tools-5.0_p9 after existing patches This patch will make mysql-gui-tools compile and run on my system. Seems like some #ifdef was erroneously commented out.
Created attachment 109576 [details] build errors on mysql-gui-tools-5.0_p9 without previous patch
The build error is already being covered in a separate bug. *** This bug has been marked as a duplicate of bug 163151 ***
