Summary: | emerge portage-2.0.50-r1 fails "miserably" | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Spider (RETIRED) <spider> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | mholzer |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Spider (RETIRED)
![]() Python-2.3 modified the path... Nothing I can do about that with the older portage version. Update portage before updating python. how about changing rdepend in portage-2.0.50 ?
>=dev-lang/python-2.2.1
Is this still a problem? And how would changing the REDEPEND in portage fix this? Portage needs to be updated first. it will always be an issue when doing a multi-step portage upgrade from 2.0.49-old to 2.0.50, when at the same time going from python 2.2 to 2.3. Can't be avoided it seems :-/ However, It also doesn't seem theres anything you can do about it Ok. I'd suggest doing what portage says after an rsync though. :-p That'd solve the problem unless you were using spython or python2.1. |