Summary: | jakarta-regexp-1.3 emerge fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Clock <clock> |
Component: | Current packages | Assignee: | Java team <java> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | olaf_j |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Clock
2005-12-13 06:19:18 UTC
After updating python you need to run python-updater. Why doesn't the emerge that upgrades the python run the python-upgrader itself? Where it is officially written that I should run python-upgrader? (In reply to comment #2) > Why doesn't the emerge that upgrades the python run the python-upgrader itself? > Where it is officially written that I should run python-upgrader? Because we lack the mechanism at the moment. python-updater calls emerge and emerge can't be called inside ebuilds. The solution for better informing the user is under work (emerge news threads on gentoo-dev). The fact that you should run python-updater is documented in einfo messages that the ebuilds shows (I agree that we can't expect users to see all these atm). It is also written in for example gwn when we put new versions stable. kestrel ~ # python-upgrader -bash: python-upgrader: command not found kestrel ~ # locate python-upgrader kestrel ~ # Doesn't work either. I ran python-upgrader and got just "command not found" message. betelgeuse@pena /usr/portage/dev-java/commons-logging $ qlist python | grep python-updater /usr/sbin/python-updater It is called python-updater not python-upgrader *** Bug 122318 has been marked as a duplicate of this bug. *** |