| 1 |
On Wednesday 12 October 2005 12:58 am, Francesco Talamona wrote: |
| 2 |
> Yesterday, after python update (dev-lang/python-2.4.1-r1), emerge |
| 3 |
> refused to work, I had to comment both lines in /etc/portage/modules |
| 4 |
> and reemerge dev-python/python-cdb. |
| 5 |
> |
| 6 |
> It wasn't a stopper, but it worth mention. |
| 7 |
|
| 8 |
That was the part I mentioned earlier. I think if you caught the note to run |
| 9 |
python-updater after the python upgrade it would have covered this. |
| 10 |
|
| 11 |
Basically what happens is that, without running python-updater, you've got a |
| 12 |
number of python packages installed in /usr/lib/python-2.3/site-packages (or |
| 13 |
something like that). |
| 14 |
|
| 15 |
After the python 2.4 upgrade, those packages are no longer available, as 2.4 |
| 16 |
is looking for them in /usr/lib/python-2.4/site-packages (or whatever). |
| 17 |
|
| 18 |
Running python-updater is supposed to get those old guys moved from 2.3 to 2.4 |
| 19 |
so everything works. |
| 20 |
|
| 21 |
Unfortunately if that message about running python-updater floats by in the |
| 22 |
middle of updating a bunch of packages it is easy to miss, and before you |
| 23 |
know it you think your system is majorly screwed. |
| 24 |
|
| 25 |
I posted a message to gentoo-dev asking for an enhancement to portage that |
| 26 |
would collect the messages generated in the pkg_postinstall phase and |
| 27 |
re-report them after all packages have completed. Fortunately it is already |
| 28 |
an enhancement that is on the list, but it's not clear when it will be |
| 29 |
released. In the meantime I'm going to check out ENOTICE |
| 30 |
http://dev.gentoo.org/~eldad/ to see if it will work as a short-term |
| 31 |
solution. |
| 32 |
-- |
| 33 |
gentoo-user@g.o mailing list |
Archives