Rich Freeman <ri...@gentoo.org> writes: > On Sun, Sep 20, 2015 at 1:24 PM, J. Roeleveld <jo...@antarean.org> wrote: >> On Sunday 20 September 2015 16:25:34 lee wrote: >>> So I decided I'd better ask what to do. It's hard to believe that we >>> are seriously expected to remove lots of software which we might not be >>> able to install again just to do an update. All these conflicts give me >>> the impression that something in the repo is broken and needs to be >>> fixed. >> >> I have no such issues, neither do most people. >> Which seems to indicate the issue is not with the repo. >> Lets look at the actual contents of your world-file. (see above) >> > > So, first, I don't think it is a good idea to just start uninstalling > packages first and then try to fix them. That might or might not > work, but it certainly isn't the first thing I'd try.
+1 > Second, this could very well be a problem with the repo, which is the > whole point of the debate around dynamic dependencies. Current > practices tend to create situations that our package managers can't > handle. They don't break for everybody instantly, which is why > they're so insidious, and also why changing the practice was somewhat > controversial when it first came up a year ago. Which means? I mean, I don't exactly have a lot of stuff installed and nonetheless "slot conflicts". Perhaps they don't matter and thereby don't classify as something that the package management couldn't handle. Now if there is something that the package management cannot handle, what messages would I get? > I hate to post it a 3rd time, but before we bicker 14 more times on > this, could somebody please just try adding --backtrack=50, and if Ok --- I haven't changed anything yet other than running emerge --sync again today: ,---- | heimdali ~ # emerge -j 8 -a --update --newuse --deep --with-bdeps=y --backtrack=500 @world | | * IMPORTANT: 4 news items need reading for repository 'gentoo'. | * Use eselect news read to view new items. | | | These are the packages that would be merged, in order: | | Calculating dependencies... done! | | !!! Multiple package instances within a single package slot have been pulled | !!! into the dependency graph, resulting in a slot conflict: | | dev-libs/boost:0 | | (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) pulled in by | (no parents that aren't satisfied by other packages in this slot) | | (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) pulled in by | dev-libs/boost:0/1.55.0= required by (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) | ^^^^^^^^^^ | (and 2 more with the same problem) | | dev-util/boost-build:0 | | (dev-util/boost-build-1.55.0:0/0::gentoo, installed) pulled in by | =dev-util/boost-build-1.55* required by (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) | ^ ^^^^^ | | (dev-util/boost-build-1.56.0:0/0::gentoo, ebuild scheduled for merge) pulled in by | =dev-util/boost-build-1.56* required by (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) | ^ ^^^^^ | | x11-drivers/nvidia-drivers:0 | | (x11-drivers/nvidia-drivers-355.11:0/0::gentoo, ebuild scheduled for merge) pulled in by | (no parents that aren't satisfied by other packages in this slot) | | (x11-drivers/nvidia-drivers-340.93:0/0::gentoo, ebuild scheduled for merge) pulled in by | ~x11-drivers/nvidia-drivers-340.93 required by (media-video/nvidia-settings-340.58:0/0::gentoo, ebuild scheduled for merge) | ^ ^^^^^^ | | media-video/ffmpeg:0 | | (media-video/ffmpeg-2.6.3:0/54.56.56::gentoo, ebuild scheduled for merge) pulled in by | (no parents that aren't satisfied by other packages in this slot) | | (media-video/ffmpeg-2.2.14:0/52.55.55::gentoo, installed) pulled in by | media-video/ffmpeg:0/52.55.55=[vdpau] required by (media-libs/mlt-0.9.0:0/0::gentoo, installed) | ^^^^^^^^^^^^ | | | 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. | | For more information, see MASKED PACKAGES section in the emerge man | page or refer to the Gentoo Handbook. | | | !!! The ebuild selected to satisfy "sci-libs/hdf5" has unmet requirements. | - sci-libs/hdf5-1.8.14-r1::gentoo USE="cxx fortran threads zlib -debug -examples -fortran2003 -mpi -static-libs -szip" | | The following REQUIRED_USE flag constraints are unsatisfied: | threads? ( !cxx !fortran ) | | The above constraints are a subset of the following complete expression: | cxx? ( !mpi ) mpi? ( !cxx ) threads? ( !cxx !mpi !fortran ) fortran2003? ( fortran ) | | (dependency required by "media-libs/openimageio-1.3.5::gentoo" [installed]) | (dependency required by "@selected" [set]) | (dependency required by "@world" [argument]) | heimdali ~ # `---- I tried without --backtrace, and it gives me the same output. > that doesn't work just try running emerge -1 on the packages that are > causing the block by depending on the older package version? I suppose the newer versions of the packages are the ones that are causing the blocks. You could argue that other versions of packages are causing the blocks, but I would argue that there weren't any blocks before the newer versions of the packages were available, hence the newer versions obviously cause the blocks. That is to say that I'm unsure which packages you're referring to as those causing the blocks. Anyway: ,---- | heimdali ~ # emerge -a -1 boost | | * IMPORTANT: 4 news items need reading for repository 'gentoo'. | * Use eselect news read to view new items. | | | These are the packages that would be merged, in order: | | Calculating dependencies... done! | [ebuild U ] sys-devel/automake-wrapper-10 [9] | [ebuild U ] dev-util/boost-build-1.56.0 [1.55.0] PYTHON_TARGETS="python2_7%*" | [ebuild r U ] dev-libs/boost-1.56.0-r1 [1.55.0-r2] PYTHON_TARGETS="python3_4* -python3_3*" | [ebuild rR ] dev-libs/librevenge-0.0.2 | [ebuild U ] dev-util/mdds-0.12.1 [0.10.3] | [ebuild rR ] app-text/libwps-0.3.1 | [ebuild NS ] sys-devel/automake-1.15 [1.11.6-r1, 1.13.4] | [ebuild r U ] dev-libs/icu-55.1 [54.1-r1] | [ebuild r U ] app-text/libetonyek-0.1.3 [0.1.1] | [ebuild rR ] app-text/libebook-0.1.2 | [ebuild rR ] media-libs/libcdr-0.1.1 | [ebuild rR ] app-text/libmspub-0.1.2 | [ebuild rR ] media-libs/libvisio-0.1.1 | [ebuild rR ] gnustep-base/gnustep-base-1.24.6-r1 | [ebuild rR ] media-libs/raptor-2.0.9 | [ebuild r U ] dev-cpp/libcmis-0.5.0-r1 [0.5.0] | [ebuild r U ] dev-libs/libixion-0.9.0 [0.7.0] PYTHON_TARGETS="python2_7%*" | [ebuild r U ] dev-libs/liborcus-0.7.1 [0.7.0] | [ebuild r U ] media-libs/harfbuzz-0.9.41 [0.9.38] USE="-fontconfig%" | [ebuild r U ] net-libs/webkit-gtk-2.4.9-r200 [2.4.8-r200] | [ebuild r U ] app-office/libreoffice-4.4.5.2 [4.4.1.2] PYTHON_TARGETS="python3_4* -python3_3*" | | The following packages are causing rebuilds: | | (dev-libs/libixion-0.9.0:0/0.10::gentoo, ebuild scheduled for merge) causes rebuilds for: | (dev-libs/liborcus-0.7.1:0/0::gentoo, ebuild scheduled for merge) | (dev-libs/icu-55.1:0/55::gentoo, ebuild scheduled for merge) causes rebuilds for: | (media-libs/harfbuzz-0.9.41:0/0.9.18::gentoo, ebuild scheduled for merge) | (media-libs/libcdr-0.1.1:0/0::gentoo, ebuild scheduled for merge) | (app-text/libebook-0.1.2:0/0::gentoo, ebuild scheduled for merge) | (media-libs/libvisio-0.1.1:0/0::gentoo, ebuild scheduled for merge) | (gnustep-base/gnustep-base-1.24.6-r1:0/0::gentoo, ebuild scheduled for merge) | (app-office/libreoffice-4.4.5.2:0/0::gentoo, ebuild scheduled for merge) | (media-libs/raptor-2.0.9:2/2::gentoo, ebuild scheduled for merge) | (net-libs/webkit-gtk-2.4.9-r200:2/2::gentoo, ebuild scheduled for merge) | (app-text/libmspub-0.1.2:0/0::gentoo, ebuild scheduled for merge) | (dev-util/mdds-0.12.1:0/0.12.1::gentoo, ebuild scheduled for merge) causes rebuilds for: | (dev-libs/libixion-0.9.0:0/0.10::gentoo, ebuild scheduled for merge) | (app-office/libreoffice-4.4.5.2:0/0::gentoo, ebuild scheduled for merge) | (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) causes rebuilds for: | (dev-cpp/libcmis-0.5.0-r1:0.5/0.5::gentoo, ebuild scheduled for merge) | (dev-libs/liborcus-0.7.1:0/0::gentoo, ebuild scheduled for merge) | (app-text/libetonyek-0.1.3:0/0::gentoo, ebuild scheduled for merge) | (app-text/libebook-0.1.2:0/0::gentoo, ebuild scheduled for merge) | (app-office/libreoffice-4.4.5.2:0/0::gentoo, ebuild scheduled for merge) | (dev-libs/librevenge-0.0.2:0/0::gentoo, ebuild scheduled for merge) | (app-text/libwps-0.3.1:0/0::gentoo, ebuild scheduled for merge) | (dev-libs/libixion-0.9.0:0/0.10::gentoo, ebuild scheduled for merge) | | !!! The following installed packages are masked: | - net-firewall/shorewall-4.6.6.2::gentoo (masked by: package.mask) | /usr/portage/profiles/package.mask: | # Ian Delaney <idel...@gentoo.org> (21 Jul 2015) | # Packages deprecated in favour of new form of | # net-firewall/shorewall | # Bug #560392 | | For more information, see the MASKED PACKAGES section in the emerge | man page or refer to the Gentoo Handbook. | | | Would you like to merge these packages? [Yes/No] `---- What should I learn from this? That we + need to update kinda recursively (because the package management can't do that for us because it's so complicated that only users with many years of experience with Gentoo can figure out how to upgrade eventually, sometimes requiring the combined effort of a mailing list), + need to rebuild (large) packages (like libreoffice) which I expect to be upgraded and thus get rebuilt later anyway (to keep the package management happy because it cannot figure this out for us and give us a choice to upgrade these (large) packages as well while we are at it), + have to do other things to keep the system up to date we somehow don't know about, like 'emerge -a --changed-deps=y @world' (because the package management doesn't really know how to update the whole system to begin with (because it's so complicated))? You see me confused. And now I don't really feel like updating anymore. But I still want to [pouts]. -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable.
