| 1 |
Sorry for the slow reply. I was expecting more people interested in |
| 2 |
sharing their insights into updating old, ancient-grade dinosaur |
| 3 |
systems. :) |
| 4 |
|
| 5 |
On 10/20/08, Brian Wince <bwince@×××××××.com> wrote: |
| 6 |
> So the -I ignores the versions of packages installed and just fixes packages |
| 7 |
> broken by a python upgrade, independent of the version? |
| 8 |
|
| 9 |
Yes, I'd think for example in terms of the difference between "emerge |
| 10 |
foo" and "emerge =foo-1.2.3". AFAICT, python-updater does the latter |
| 11 |
by default, but with the -i option it is given a permission to do the |
| 12 |
former "within a slot". |
| 13 |
|
| 14 |
Since most packages only have a single slot, the "within a slot" |
| 15 |
becomes irrelevant for them. |
| 16 |
|
| 17 |
> I understand that slots can be used to install different versions of an app |
| 18 |
> but not sure how that relates to python-updater. |
| 19 |
|
| 20 |
Sorry if I lead you too much into this slot territory. The slots are |
| 21 |
more of a red herring here, or just a small, distracting detail. For |
| 22 |
most packages slots "won't matter". |
| 23 |
|
| 24 |
But there are the few, like qt, for which it is important to keep |
| 25 |
within a slot. Therefore it is nice that helpful scripts, like |
| 26 |
python-updater, try to provide automagic support for the slotting |
| 27 |
related stuff where it is needed. |
| 28 |
|
| 29 |
Still, python-updater -i is not guaranteed to fix your original |
| 30 |
problem, it was just a suggestion. The problem might not even lay with |
| 31 |
libxml2, but one of its dependencies, their dependencies, or |
| 32 |
dependencies of python itself. |
| 33 |
|
| 34 |
If you haven't already tried it, then revdep-rebuild from the |
| 35 |
gentoolkit package is your other friend. You might need try running it |
| 36 |
first and then retry with the python-updater. |
| 37 |
|
| 38 |
-- |
| 39 |
Arttu V. |
Archives