|Summary:||sys-apps/portage: dev-libs/boost update triggers conflicts with slot-operator deps when not updating @world|
|Product:||Portage Development||Reporter:||G.Wolfe Woodbury <redwolfe>|
|Component:||Core||Assignee:||Portage team <dev-portage>|
|Severity:||major||CC:||cornicx, redwolfe, xms-00|
|Package list:||Runtime testing required:||---|
emerge --info for dev-libs/boost
full portage output from update attemmpt
full portage output from update attemmpt
Full emerge screen output for attempt 2017-02-13:0440EST
Description G.Wolfe Woodbury 2017-01-26 05:42:17 UTC
Created attachment 461456 [details] emerge --info for dev-libs/boost The newest dev-libs/boost (and dev-util/boost-build) will not update due to conflicts with other packages. The packages generally want the exact version of boost == 1.62.0. The list I have at the moment is: dev-libs/boost:0/1.62.0= required by (dev-util/mdds-1.2.2:1/1.2::gentoo dev-libs/boost:0/1.62.0= required by (dev-util/mdds-0.12.1:0/0.12.1::gentoo dev-libs/boost:0/1.62.0=[threads] required by (media-sound/mp3diags-1.2.03-r1:0/0::gentoo dev-libs/boost:0/1.62.0= required by (dev-db/mysql-connector-c++-1.1.6:0/0::gentoo dev-libs/boost:0/1.62.0=[abi_x86_64(-),threads] required by (net-libs/nghttp2-1.19.0:0/1.14::gentoo dev-libs/boost:0/1.62.0=[threads] required by (dev-libs/libixion-0.11.1:0/0.11::gentoo dev-libs/boost:0/1.62.0= required by (dev-libs/librevenge-0.0.4:0/0::gentoo >=dev-libs/boost-1.55:0/1.62.0= required by (app-office/libreoffice-188.8.131.52:0/0::gentoo dev-libs/boost:0/1.62.0= required by (dev-cpp/libcmis-0.5.2_pre20160820:0.5/0.5::gentoo >=dev-libs/boost-1.51.0:0/1.62.0= required by (dev-libs/liborcus-0.11.2:0/0.11::gentoo >=dev-libs/boost-1.46.0:0/1.62.0= required by (media-video/mkvtoolnix-9.8.0:0/0::gentoo These packages requiring the exact slot foil usual methods to work around installing newer packages. I suggest a tracker bug or something. libgit2 and xorg-server face similar problems with some packages.
Comment 1 Michael Palimaka (kensington) 2017-01-26 09:54:27 UTC
Could you please add the full portage output? The info in comment #0 seems to be just a subset and strangely formatted. =
Comment 2 G.Wolfe Woodbury 2017-01-26 21:22:44 UTC
I will, the line in #0 are just the parts of the output that show the reason for the conflict. Sorry about the confusion.
Comment 3 G.Wolfe Woodbury 2017-01-26 21:57:57 UTC
Created attachment 461532 [details] full portage output from update attemmpt
Comment 4 G.Wolfe Woodbury 2017-01-26 21:57:57 UTC
Created attachment 461534 [details] full portage output from update attemmpt
Comment 5 G.Wolfe Woodbury 2017-01-26 22:01:53 UTC
I had a browser or mind mess-up that resulted in multiple attachments of the same file. Carry on as usual. Sorry.
Comment 6 Adam Feldman 2017-02-10 23:02:49 UTC
To me, this just looks like a slot rebuild issue. All of the "conflicting" packages just need to be rebuilt with the new subslot of boost. I believe using --backtrack=30 should fix it as suggested in the portage output. Alternatively, as a worst case, manual intervention, you could try one shotting all of the conflicts with the offending package, ie emerge -1 boost boost-build mdds md3diags etc See https://wiki.gentoo.org/wiki/Troubleshooting#Dependency_graph_slot_conflicts for a full description of the procedure. If this resolves it, feel free to close out the bug.
Comment 7 Michael Palimaka (kensington) 2017-02-11 09:52:22 UTC
I'm not certain if this is supposed to "just work" or if we normally expect to use extra options to resolve a conflict like this - hopefully the portage team can reclassify this bug more accurately.
Comment 8 Zac Medico 2017-02-11 10:42:04 UTC
(In reply to G.Wolfe Woodbury from comment #3) > Created attachment 461532 [details] > full portage output from update attemmpt The problem is that you need to perform updates like this with --update --deep @world, since "partial" updates like this are not really supported until bug 559354 has been implemented. The problem is that emerge doesn't trigger the necessary rebuilds because it assumes you don't want them, and we currently don't have a way to tell it differently, except by using --update --deep @world.
Comment 9 Zac Medico 2017-02-11 10:49:07 UTC
You might encounter bug 554838, but you can probably get around it by using the command in bug 554838, comment #34.
Comment 10 Zac Medico 2017-02-11 10:53:29 UTC
(In reply to Zac Medico from comment #9) > You might encounter bug 554838, but you can probably get around it by using > the command in bug 554838, comment #34. If the command in bug 554838, comment #34 doesn't work, then you will likely need to follow the troubleshooting method from the FAQ which I mentioned in bug 554838, comment #28: https://wiki.gentoo.org/wiki/Project:Portage/FAQ#What_should_I_do_when_emerge_reports_a_lot_of_dependency_conflicts_involving_built_slot-operator_.28foo.2Fbar:X.2FY.3D.29_dependencies.3F
Comment 11 Zac Medico 2017-02-12 04:35:51 UTC
*** Bug 607678 has been marked as a duplicate of this bug. ***
Comment 12 G.Wolfe Woodbury 2017-02-13 09:46:31 UTC
Created attachment 463576 [details] Full emerge screen output for attempt 2017-02-13:0440EST We are back to square 1. This is for updating to boost-1.63.0 (not 1.62.xxx) and all the slot operators are explicit. I tried the several workarounds and methods mentioned here and in other places. Certain packages are requiring 1.62.xxx and not allowing upgrade to boost-1.63.0 This is going to hang on until the conflicting packages allow the newer boot when building.
Comment 13 Zac Medico 2017-02-13 09:54:00 UTC
(In reply to G.Wolfe Woodbury from comment #12) > Created attachment 463576 [details] > Full emerge screen output for attempt 2017-02-13:0440EST Does it solve with --pretend --ignore-built-slot-operator-deps=y --backtrack=0 or not? You need to try that in order to rule out configuration issues hidden by backtracking, as discussed in the FAQ.
Comment 14 G.Wolfe Woodbury 2017-02-13 12:28:20 UTC
That was tried to no avail. HOWEVER: the /var/db/pkg/dev-util had a stray entry for mdds-0.12.1 sitting around and the system could not get its head around that until the entry was resolved. boost is now happily updating
Comment 15 Zac Medico 2017-02-13 17:28:40 UTC
(In reply to G.Wolfe Woodbury from comment #14) > HOWEVER: the /var/db/pkg/dev-util had a stray entry for mdds-0.12.1 sitting > around and the system could not get its head around that until the entry was > resolved. In the next portage release, we have a new warning message for packages like those that can't be rebuilt. That makes this a duplicate of bug 602964. *** This bug has been marked as a duplicate of bug 602964 ***