emerge -uDp world gives me this: [ebuild UD] dev-lang/python-2.2.2-r1 [2.2.3] however, if I do this downgrade, the next emerge -uDp world will want to upgrade, thus creating a continual loop. Reproducible: Always Steps to Reproduce:
yep, keeps happening on one of my boxes as well -- little annoying
its kportage .. its pegging itself to python-2.2.2 .. /me grumbles and fixes .. mcvaio ~ % etcat depends python-2.2.2 [ Results for search key : python-2.2.2 ] * app-admin/kportage-0.6.1 ~dev-lang/python-2.2.2 * app-admin/kportage-0.6 ~dev-lang/python-2.2.2
Yup .. here too except kportage does not run with 2.2.3 so I've had to push it back manually. there is patch in bug 22660 for kportage to fix the dependency
but i'm not sure that it allows kportage to run with pythin 2.2.3.
everytime I've tried to run kportage with python 2.2.3 installed it crashes without presenting a screen. All I see is the icon 'spin' until it dies. re-emerging 2.2.2 brings back kportage function. however using the attachment (revised ebuild in bug 22660) and building with python 2.2.3 kportage does run properly. (generating all the proper digests before the emerge first of course) so an upgrade in python to 2.2.3 should trigger and automatic recompile of kportage to 'version 0.6.1-r1' or else kportage will not function maintianers take note of the above please
At least, my patch works for me: http://bugs.gentoo.org/show_bug.cgi?id=22660 See it in action: http://www.mundolink.net/users/mariov/mydesktop3.jpg http://www.mundolink.net/users/mariov/mydesktop4.jpg
derk, which patch are you talking about? the ebuild in bug 22660 is exact the same as the one currently in portage? do you mean we need to re-emerge kportage to fix it?
I re-emerged kportage this morning against python 2.2.3 and got a seg fault from kde after trying to run kportage: bash-2.05b$ cat /home/roger/kportagesegfault.txt (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 12128)] 0x410bd1c7 in waitpid () from /lib/libpthread.so.0 #0 0x410bd1c7 in waitpid () from /lib/libpthread.so.0 #1 0x406fd0ac in KCrash::defaultCrashHandler(int) () from /usr/kde/3.1/lib/libkdecore.so.4 #2 0x410bc03c in __pthread_sighandler () from /lib/libpthread.so.0 #3 <signal handler called> #4 0x080a8ba3 in PortagePython::stringFromClassMethod(char*, char*, _object*) () #5 0x080a8f12 in PortagePython::readConfig() () #6 0x080c2924 in ParseMakeConfs::readConfig() () #7 0x080c20af in ParseMakeConfs::ParseMakeConfs(QMap<QString, QString>*) () #8 0x080b6c2c in Config::Config() () #9 0x080b6f26 in Config::instance() () #10 0x0808952e in KPortageApp::initActions() () #11 0x08086b43 in KPortageApp::KPortageApp(QWidget*, char const*) () #12 0x0808f31e in main () #13 0x4114b7a7 in __libc_start_main () from /lib/libc.so.6
this isn't a python problem, its a kportage problem now. marking as a dup of the kportage bug. *** This bug has been marked as a duplicate of 22660 ***
I know this seems odd but if you use the patched ebuild from 22660 which just changes the dependency it builbs kportage fine and kportage runs. If you don't use the patched ebuild and try to build it with python 2.2.3 it crashes .. if kportage was built against python 2.2.2 and python 2.2.3 is then installed .. kportage will not run .. start up spin and dies. At least that is the experience on my machine and set-up .. I'm generally using '~x86' all the time .. except when a software problem occurs then I back-out the offending version.. derk
