| 1 |
>> Tetex 2.0-r1 has been removed from portage. It looks like emerge |
| 2 |
>> tries to be on the safe side and rather downgrade than keep |
| 3 |
>> a version it does not know about. If you upgrade to tetex-2.0.2, |
| 4 |
>> emerge -U should no longer try to downgrade. |
| 5 |
|
| 6 |
> Thank you very much! That explains it and your suggestion fixed the |
| 7 |
> problem. However, is this really the _right_ behaviour? |
| 8 |
|
| 9 |
This is proper behavior. You are crossing borders from Stable to |
| 10 |
unstable. Portage NEVER crosses that border without being told to |
| 11 |
explicitly, which is why you have to specify ~x86. |
| 12 |
|
| 13 |
You're attempting to update a package from inside the Stable |
| 14 |
branch in your first attempt. Portage only sees one possibility |
| 15 |
because it will not assume that you meant to stay in ~x86 even |
| 16 |
though the package was previously merged that way. |
| 17 |
|
| 18 |
This behavior will change slightly in the 2.1 series of portage. |
| 19 |
|
| 20 |
--NJ |
Archives