View previous topic :: View next topic |
Author |
Message |
tristen n00b
Joined: 29 Jul 2011 Posts: 16 Location: Heidelberg, Germany
|
Posted: Sun May 15, 2016 3:47 pm Post subject: qt 4 mysql conflict |
|
|
I'm trying to re-emerge qt 4 after de-kewording and I'm running into something a bit baffling:
!!! 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-r8:0/18::gentoo, installed) pulled in by
=virtual/mysql-5.6-r8[embedded?] required by (dev-perl/DBD-mysql-4.32.0-r1:0/0::gentoo, installed)
^ ^^^^^^
=virtual/mysql-5.6-r8 required by (app-office/akonadi-server-1.13.0-r2:0/0::gentoo, installed)
^ ^^^^^^
=virtual/mysql-5.6-r8[embedded=,static=] required by (dev-db/mariadb-10.1.14:0/18::gentoo, installed)
^ ^^^^^^
(virtual/mysql-5.6-r7:0/18::gentoo, ebuild scheduled for merge) pulled in by
>=virtual/mysql-5.6-r2:=[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?] required by (dev-qt/qtsql-4.8.6-r1:4/4::gentoo, ebuild scheduled for merge)
Can somebody explain what the actual conflict is here? To me it looks like virtual/mysql-5.6-r8:0/18 should be compatible with >=virtual/mysql-5.6-r2:= . What am I missing here? |
|
Back to top |
|
|
skiwarz Apprentice
Joined: 23 Feb 2014 Posts: 263
|
Posted: Tue May 17, 2016 1:12 am Post subject: |
|
|
Try un-keywording virtual/mysql if you can
If that doesn't work, then try masking either mysql-5.6-r7 or -r8. Looking at the ebuilds, I can't figure out why it says "=virtual/mysql-5.6-r8" because those three packages don't specify a version. But I'm probably missing something.
Or just try unmerging one or both of the mysql's and see what portage pulls in automatically.
Let me know if this works |
|
Back to top |
|
|
tristen n00b
Joined: 29 Jul 2011 Posts: 16 Location: Heidelberg, Germany
|
Posted: Wed May 18, 2016 6:27 am Post subject: |
|
|
Thanks for your reply. In the end I keyworded the slot (ie, dev-qt/<name>:4) and then the conflict disappeared. Maybe it was because I had virtual/mysql keyworded as you suggest? Anyhow, now my priority is to try to salvage my failed migration to plasma 5. |
|
Back to top |
|
|
skiwarz Apprentice
Joined: 23 Feb 2014 Posts: 263
|
Posted: Wed May 18, 2016 2:18 pm Post subject: |
|
|
Good luck! Glad it worked |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|