libgda blocks newer mariadb versions, because of the following rule in the ebuild: RDEPEND="... mysql? ( virtual/mysql:= ) ... " That leads to: emerge --update -avt1 mariadb virtual/mysql These are the packages that would be merged, in reverse order: Calculating dependencies... done! [ebuild U ~] virtual/mysql-5.6-r1:0/18 [5.6:0/0] USE="-embedded -minimal -static -static-libs" 0 kB Total: 1 package (1 upgrade), Size of downloads: 0 kB !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: virtual/mysql:0 (virtual/mysql-5.6-r1::gentoo, ebuild scheduled for merge) pulled in by =virtual/mysql-5.6-r1 required by (dev-libs/redland-1.0.16::gentoo, installed) (and 19 more with the same problem) (virtual/mysql-5.6::gentoo, installed) pulled in by virtual/mysql:0/0= required by (gnome-extra/libgda-5.2.2::gentoo, installed) Reproducible: Always I changed this for testing to: RDEPEND="... mysql? ( virtual/mysql ) ... " Emerging libgda with this change stops blocking newer virtual/mysql and dev-db/mariadb in the second step. Emerging of libgda with those newer packages in a third step works without problems too.
This could be a portage bug, please retry with latest portage and provide emerge --info output
Meanwhile there were a few portage updates. I reemerged libgda, than mariadb and virtual/mysql and all worked well. The difference: Now I had no old version to update, so it may not be a meaningful test. Next real update of mariadb I will try again.
Then, feel free to reopen when you are able to reproduce with the concrete error and the --info output :/
