kportage-0.6.1.ebuild has a physical dependency of python-2.2.2, when it works with python 2.2.3. Reproducible: Always Steps to Reproduce: 1. Emerge python greater than 2.2.2 2. Try to emerge kportage Actual Results: Emerge will downgrade your python to 2.2.2 Expected Results: kportage should emerge without problems
Created attachment 13142 [details] fixed python 2.2.3 dependency.
kportage does not run with 2.2.3 in my experience. Does it need to be compiled against it?
see also bug 22764
yup kportage needs the recompile against 2.2.3 or it will not run. see other comments in bug 22764
*** Bug 22764 has been marked as a duplicate of this bug. ***
so kportage works after recompiling with python 2.2.3, right? i don't have kde, so i need one of the kde guys to check this out.
I compiled kportage-0.6.1 against python 2.2.3 and I got a seg fault when trying to run kportage. Mario Vazquez's fix - kportage-0.6.1-r1- is not in portage yet so I haven't tried to compile it. Mario says he fixed the python dependency problem and kportage -r1 will compile against python-.2.2.3.
I tried, but it goes so slow for me (I presume it's caching the portage directories) that it's unbearable to sit and wait. I'll retry again at home and see what happens there.
Okay, the python dependency problem has been fixed for a few days now. A re-emerge of kportage seems to work fine for me. Closing as FIXED.
It may be fixed for you but not for me. I unmerged kportage and then emerged Kportage-0.6.1. The emerge succeeded but when I tried to run kportage I still get a seg fault from kde.Here is the KDE Crash Handler Backtrace. (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 24353)] 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 I am using python-2.2.3
Running kportage from konsole - bash-2.05b$ kportage Could not find platform independent libraries <prefix> Could not find platform dependent libraries <exec_prefix> Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>] 'import site' failed; use -v for traceback kportage: Can't load module This is beyond me.
