On 2013-08-14 03:06, Thomas Kahle wrote:
On 08/13/2013 04:56 PM, Thomas Kahle wrote:
Hi,
recently my sage-on-gentoo started to crash on startup. Something is
wrong with babel as can be seen in the end of the attached
crash-report.
Any ideas?
For what it's worth, I also found this in my world update messages:
WARNING: One or more updates have been skipped due to a dependency
conflict:
dev-python/jinja:0
(dev-python/jinja-2.7::gentoo, ebuild scheduled for merge) conflicts
with
=dev-python/jinja-2.3[-python_single_target_python2_5(-),-python_single_target_python3_1(-),python_targets_python3_2(-),-python_single_target_python3_2(-)]
required by (dev-python/sphinx-1.1.3-r7::gentoo, installed)
The sphinx dep is also through sage...
I think that's a different problem.
The main issue is that jinja-2.7+ supports python 3.3 but not 3.1 or
3.2.
So if you have python 3.2 installed you cannot upgrade to jinja 2.7.
You would need jinja 2.7 and jinja 2.6-r100 which is in another slot to
cover
python 3.1 and 3.2 and that doesn't seem to be fully in place yet.
There may be other issues.
And as of my syncing this morning the message disappeared. It may also
be that you
have jinja in your world file which will trigger an upgrade request that
will be
shot down by the sphinx dependency.
emerge --deselect jinja
may solve that particular message.
Francois
