1 |
I wouldn't recommend this approach. This will probably break whatever package depends on |
2 |
the older version of the flip-flopping package. |
3 |
|
4 |
Paul Fraser wrote: |
5 |
> You could use emerge -UDp instead, which will tell Portage to ignore any downgrades that may occur, and only show packages that will actually be updated. |
6 |
> |
7 |
> On Sat, Oct 25, 2003 at 12:58:28PM -0500, Andrew Gaffney wrote: |
8 |
> |
9 |
>>Ruben Vermeersch wrote: |
10 |
>> |
11 |
>>>Ok, here's what's bugging me lately: |
12 |
>>> |
13 |
>>> ruben@neferteti ruben $ emerge -uDp world |
14 |
>>> |
15 |
>>> These are the packages that I would merge, in order: |
16 |
>>> |
17 |
>>> Calculating world dependencies ...done! |
18 |
>>> [ebuild U ] x11-libs/wxGTK-2.4.1-r1 [2.4.0] |
19 |
>>> |
20 |
>>>After updating wxGTK, i stumble upon this: |
21 |
>>> |
22 |
>>> neferteti ruben # emerge -uDp world |
23 |
>>> |
24 |
>>> These are the packages that I would merge, in order: |
25 |
>>> |
26 |
>>> Calculating world dependencies ...done! |
27 |
>>> [ebuild UD] x11-libs/wxGTK-2.4.0 [2.4.1-r1] |
28 |
>>> |
29 |
>>>Something tells me this ain't normal behaviour :) |
30 |
>> |
31 |
>>I've seen this kind of thing a few times before, most notably with avifile |
32 |
>>and drip. In this case, there is an update available for wxGTK, so portage |
33 |
>>upgrades it. Unfortunately, there is some program installed that requires |
34 |
>>on a version of wxGTK <=2.4.0, so portage downgrades it to not break the |
35 |
>>other program. I consider this behavior a portage bug, but as far as I |
36 |
>>know, there is currently no easy way to prevent this from happening. |
37 |
>> |
38 |
>>-- |
39 |
>>Andrew Gaffney |
40 |
>> |
41 |
>> |
42 |
>>-- |
43 |
>>gentoo-dev@g.o mailing list |
44 |
> |
45 |
> |
46 |
|
47 |
|
48 |
-- |
49 |
Andrew Gaffney |
50 |
|
51 |
|
52 |
-- |
53 |
gentoo-dev@g.o mailing list |