Summary: | Upgrading python-2.2 to python-2.3 breaks portage | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stuart Herbert (RETIRED) <stuart> |
Component: | [OLD] Core system | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | dev-portage |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Stuart Herbert (RETIRED)
2004-04-12 04:49:52 UTC
portage-2.0.49-r16+ works with both python-2.3 and python-2.2. So you need to upgrade portage to a newer version before upgrading python. We used to have a check on the portage version in the python ebuild, but this check created a nasty circular dependency between portage and python when installing. I'd love a good solution to this problem but the portage and python teams haven't been able to come up with something better than what we have now. Okay, how about putting a blocker in python-2.3, so that you can't upgrade unless you're running one of the safe 2.0.49 releases of Portage? It'd be annoying, but not as annoying as the current situation. Or, provide a python-config tool, and force the user to switch from python-2.2 to python-2.3 manually by using the tool? Again, annoying, but not the end of the world. I don't know python too well, but surely there's a way to have new versions of python automatically pick up classes installed with older versions? That's what is at the heart of the problem. Is this a python design problem, or just down to the way we lay out python once installed? Best regards, Stu Liquidx committed a python-2.3.3.ebuild a while ago that's supposed to fix this problem. We still need some testing of this afaik. I'll see if I have a box still running python-2.2 and portage <2.0.49-r16. |