Summary: | dev-python/PyQt4-4.3 failed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michal Jakubowski <daemon> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | aikawarazuni, alan.mckinnon, bela.hausmann, ed, faccin.giovani, floriangys, hamburglar6, jan.bednar, kentnl, njdoyle+bugs |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Michal Jakubowski
2007-09-07 20:55:52 UTC
Running python-updater after upgrading python is not optional. (In reply to comment #1) > Running python-updater after upgrading python is not optional. > I haven't python-updater AG1S / # python-updater -su: python-updater: command not found (In reply to comment #2) > (In reply to comment #1) > > Running python-updater after upgrading python is not optional. > > > I haven't python-updater > AG1S / # python-updater > -su: python-updater: command not found > OK i have ;-) (In reply to comment #3) > (In reply to comment #2) > > (In reply to comment #1) > > > Running python-updater after upgrading python is not optional. For the record, I also got bitten by this "bug", so I'm posting here to alert future users. My python was updated to 2.5, I didn't see the notice to use python-updater and (IIRC) 'emerge --depclean' removed python-2.4 shortly thereafter. python-updater then exits with a "* Can't determine any previous Python version(s)" message. To get PyQt4 to merge, I had to re-emerge python-2.4, then run python-updater, which only then put PyQt4 in it's list and emerged it correctly. "python-updater -o 2.4" will do the trick too. *** Bug 192870 has been marked as a duplicate of this bug. *** *** Bug 193280 has been marked as a duplicate of this bug. *** *** Bug 193370 has been marked as a duplicate of this bug. *** *** Bug 218874 has been marked as a duplicate of this bug. *** *** Bug 265525 has been marked as a duplicate of this bug. *** *** Bug 266149 has been marked as a duplicate of this bug. *** Earlier versions of PyQt also have this "problem". Today I had trouble emerging PyQt-3.17.6 which is pulled in by amarok. It was easily solved by running python-updater. *** Bug 405119 has been marked as a duplicate of this bug. *** Perhaps PyQT and PyKDE ( which dies the same way ) can be enhanced to produce this suggestion when this error occurs? I don't really "use" my python installation apart from portage, so not knowing it had been updated at some stage because I didn't happen to see the notice, leading to a "broken" configuration is sub-optimal. Perhaps when python is updated it can write a file that allows other things to know python has been updated, and other python-depending packages can notice that this file is present, and warn the user that python has been updated but python updater hasn't been run, and running python-updater can remove the file that triggers this warning? |