| 1 |
On Sat, Sep 19, 2015 at 3:57 PM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 2 |
> On 19/09/2015 21:36, lee wrote: |
| 3 |
>> |
| 4 |
>> dev-libs/boost:0 |
| 5 |
>> |
| 6 |
>> (dev-libs/boost-1.56.0-r1:0/1.56.0::gentoo, ebuild scheduled for merge) pulled in by |
| 7 |
>> (no parents that aren't satisfied by other packages in this slot) |
| 8 |
>> |
| 9 |
>> (dev-libs/boost-1.55.0-r2:0/1.55.0::gentoo, ebuild scheduled for merge) pulled in by |
| 10 |
>> dev-libs/boost:0/1.55.0= required by (dev-libs/librevenge-0.0.2:0/0::gentoo, installed) |
| 11 |
>> ^^^^^^^^^^ |
| 12 |
>> (and 2 more with the same problem) |
| 13 |
> |
| 14 |
> I'm not sure why you are getting this one. Portage is only pulling in |
| 15 |
> boost-1.56.0-r1 because it's the latest stable version, but librevenge |
| 16 |
> requires something earlier. Portage should therefore shut up and install |
| 17 |
> the only real solution - keep boost at 1.55.0 |
| 18 |
> |
| 19 |
|
| 20 |
librevenge doesn't require an earlier version. This is either a |
| 21 |
result of insufficient backtracking, or it might have to do with how |
| 22 |
portage stores runtime dependencies for installed packages. |
| 23 |
|
| 24 |
Try adding --backtrack=50 to your command line and try again. If |
| 25 |
nothing else it might simplify the output. It will take longer to |
| 26 |
run. |
| 27 |
|
| 28 |
If it is the rdepend issue then you can probably emerge -1 librevenge |
| 29 |
and whatever else is depending on the old version to fix it. |
| 30 |
|
| 31 |
Also, emerge running --changed-deps=y from time to time may make those |
| 32 |
kinds of problems less likely. The first time you do it prepare to |
| 33 |
see a LOT of stuff get rebuilt - any of those packages could cause |
| 34 |
issues in the future but most probably will not. |
| 35 |
|
| 36 |
> You fail to understand how gentoo works. At no time did Gentoo ever |
| 37 |
> guarantee that updates would work like binary distros and the process |
| 38 |
> would be trouble free. Quite the opposite - Gentoo is upfront in telling |
| 39 |
> you that there will always be update issues and you are the person to |
| 40 |
> solve them. |
| 41 |
> |
| 42 |
|
| 43 |
While Gentoo doesn't do as much handholding as many distros, the |
| 44 |
portage output above should not be viewed as something we are proud |
| 45 |
of. |
| 46 |
|
| 47 |
--backtrack fixes a lot of issues, and there aren't a lot of simple |
| 48 |
solutions for that without slowing down emerge. |
| 49 |
|
| 50 |
On the other hand, a lot of the runtime dependency issues could be |
| 51 |
fixed. There is a discussion on -dev right now about getting rid of |
| 52 |
dynamic runtime deps, which would probably help cut down on some of |
| 53 |
the more bizarre behavior. |
| 54 |
|
| 55 |
-- |
| 56 |
Rich |
Archives