| 1 |
On 2013-08-14 03:06, Thomas Kahle wrote: |
| 2 |
> On 08/13/2013 04:56 PM, Thomas Kahle wrote: |
| 3 |
>> Hi, |
| 4 |
>> |
| 5 |
>> recently my sage-on-gentoo started to crash on startup. Something is |
| 6 |
>> wrong with babel as can be seen in the end of the attached |
| 7 |
>> crash-report. |
| 8 |
>> Any ideas? |
| 9 |
> |
| 10 |
> For what it's worth, I also found this in my world update messages: |
| 11 |
> |
| 12 |
> WARNING: One or more updates have been skipped due to a dependency |
| 13 |
> conflict: |
| 14 |
> |
| 15 |
> dev-python/jinja:0 |
| 16 |
> |
| 17 |
> (dev-python/jinja-2.7::gentoo, ebuild scheduled for merge) conflicts |
| 18 |
> with |
| 19 |
> |
| 20 |
>> =dev-python/jinja-2.3[-python_single_target_python2_5(-),-python_single_target_python3_1(-),python_targets_python3_2(-),-python_single_target_python3_2(-)] |
| 21 |
> required by (dev-python/sphinx-1.1.3-r7::gentoo, installed) |
| 22 |
> |
| 23 |
> The sphinx dep is also through sage... |
| 24 |
I think that's a different problem. |
| 25 |
The main issue is that jinja-2.7+ supports python 3.3 but not 3.1 or |
| 26 |
3.2. |
| 27 |
So if you have python 3.2 installed you cannot upgrade to jinja 2.7. |
| 28 |
You would need jinja 2.7 and jinja 2.6-r100 which is in another slot to |
| 29 |
cover |
| 30 |
python 3.1 and 3.2 and that doesn't seem to be fully in place yet. |
| 31 |
There may be other issues. |
| 32 |
|
| 33 |
And as of my syncing this morning the message disappeared. It may also |
| 34 |
be that you |
| 35 |
have jinja in your world file which will trigger an upgrade request that |
| 36 |
will be |
| 37 |
shot down by the sphinx dependency. |
| 38 |
emerge --deselect jinja |
| 39 |
may solve that particular message. |
| 40 |
|
| 41 |
Francois |
Archives