On Sat, Sep 19, 2015 at 3:57 PM, Alan McKinnon <alan.mckin...@gmail.com> wrote: > On 19/09/2015 21:36, lee wrote: >> >> 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) > > I'm not sure why you are getting this one. Portage is only pulling in > boost-1.56.0-r1 because it's the latest stable version, but librevenge > requires something earlier. Portage should therefore shut up and install > the only real solution - keep boost at 1.55.0 >
librevenge doesn't require an earlier version. This is either a result of insufficient backtracking, or it might have to do with how portage stores runtime dependencies for installed packages. Try adding --backtrack=50 to your command line and try again. If nothing else it might simplify the output. It will take longer to run. If it is the rdepend issue then you can probably emerge -1 librevenge and whatever else is depending on the old version to fix it. Also, emerge running --changed-deps=y from time to time may make those kinds of problems less likely. The first time you do it prepare to see a LOT of stuff get rebuilt - any of those packages could cause issues in the future but most probably will not. > You fail to understand how gentoo works. At no time did Gentoo ever > guarantee that updates would work like binary distros and the process > would be trouble free. Quite the opposite - Gentoo is upfront in telling > you that there will always be update issues and you are the person to > solve them. > While Gentoo doesn't do as much handholding as many distros, the portage output above should not be viewed as something we are proud of. --backtrack fixes a lot of issues, and there aren't a lot of simple solutions for that without slowing down emerge. On the other hand, a lot of the runtime dependency issues could be fixed. There is a discussion on -dev right now about getting rid of dynamic runtime deps, which would probably help cut down on some of the more bizarre behavior. -- Rich
