| 1 |
Helmut Jarausch wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I'm using portage-2.2_rc33. And it has become smarter with every new |
| 5 |
> release. Still, I don't understand why it's sometimes smarter than other |
| 6 |
> times. |
| 7 |
> |
| 8 |
> In most cases now, it's able to handle cases where installed old |
| 9 |
> packages which depend on, say, libXX-version-1, block emerging |
| 10 |
> libXX-version-2 by unmerging the old version itself. |
| 11 |
> |
| 12 |
> But sometimes, like today when upgrading from various qt-...-4.5.1 |
| 13 |
> to qt-...-4.5.2 packages it produces tons of blockings which it |
| 14 |
> cannot resolve itself. |
| 15 |
> |
| 16 |
> How can I help portage to resolve this blockings itself in a smart way? |
| 17 |
> (trying to do |
| 18 |
> emerge --keep-going -j2 -1 --ask --update --newuse --deep @system @world |
| 19 |
> automatically. |
| 20 |
> ) |
| 21 |
> |
| 22 |
> Many thanks for a hint, |
| 23 |
> Helmut. |
| 24 |
> |
| 25 |
> |
| 26 |
|
| 27 |
Another thought to. The option --with-bdeps y may help. It may not but |
| 28 |
it could be worth a try. I have ran into problems where that helped and |
| 29 |
have read where a few others have ran into similar problems and that |
| 30 |
fixed it. It just tells emerge to dig a little deeper from my |
| 31 |
understanding. |
| 32 |
|
| 33 |
Can't think of anything else at the moment. |
| 34 |
|
| 35 |
Dale |
| 36 |
|
| 37 |
:-) :-) |
Archives