The alacarte-0.10.2 ebuild fails to emerge on a system w/ pygtk-2.10: checking for pygtk 2.8.0 installed for python 2.4... not found configure: error: required pygtk version not found Reproducible: Always Expected Results: The ebuild should be updated to: * Include req for <=pygtk-2.8 * Patched to allow pygtk >= 2.8
Works fine here. Can you post the config.log that portage asked you to post when it failed?
Created attachment 119755 [details] Config.log for alacarte
Looking at the system more, it looks like it used python 2.4 rather than the installed 2.5. Any reasons why alacarte cannot use python 2.5? Would it be preferable to unmerge python 2.4?
You probably need to run pthon-updater.
(In reply to comment #4) > You probably need to run pthon-updater. > python-updater failed to re-emerge alacarte. I do have pygtk-2.10 installed under python 2.5. In fact, pyhton-updater succeeded for all but alacarte. Unmasking new version of alacarte didn't help.
I just emerged python and python-updater "Can't determine any previous Python version(s). thankfully you can still mask alacarte since equery says there are no dependencies package.mask >x11-misc/alacarte-0.10.1-r1 works just fine
Sorry nope, that isn't going to work the current version alacarte-0.10.2 requires python-2.8 Maybe the requirement for gnome should be changed since it doesn't seem to affect it?
No, actually, it doesn't. I just built alacarte-0.10.2 against pygtk-2.10.4 perfectly fine. It's a problem with your python 2.5, most likely. I don't know why python-updater failed. It was substantially chaged recently, maybe they've fixed the bug? At any rate, try re-emerging alacarte after you've re-emerged pygtk.
Same problem after emerging pygtk again: checking pkg-config is at least version 0.9.0... yes checking for ALACARTE... yes checking for pygtk 2.8.0 installed for python 2.4... not found configure: error: required pygtk version not found Even though: > emerge -pv pygtk These are the packages that would be merged, in order: Calculating dependencies ..... ..... ..... ..... done! [ebuild R ] dev-python/pygtk-2.10.4 USE="opengl -doc -examples" 0 kB
Are you, in fact, using python 2.5? If so, do you still have python 2.4 slotted? Alacarte checks for python as 2.4, 2.4.0, 2.5, then 2.5.0. So, if you have 2.4 (which it seems you do), it will look for pygtk in python 2.4, and *not* in 2.5. I only have 2.4, as this is the only stable version.
I have the same problem even after running python-updater. slotted python : python-2.4.4-r4 python-2.5-r1 and pygtk-2.10.4 ---------------------------------------------------------- checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for ALACARTE... yes checking for pygtk 2.8.0 installed for python 2.4... not found configure: error: required pygtk version not found
This is because python-updater works the opposite of alacarte: it makes all the installed python libs use python 2.5, while alacarte trys 2.4 and fails. You would have to uninstall python 2.4 before alacarte would work. If I get a chance, I'll work on a solution, but I don't have any python 2.5 boxes at the moment, so it may take time.
Unmerging python-2.4 worked fine. Thanks
Created attachment 121450 [details, diff] Patch that hopefully solves python2.5 and pygtk problem in configure part (In reply to comment #12) > This is because python-updater works the opposite of alacarte: it makes all the > installed python libs use python 2.5, while alacarte trys 2.4 and fails. You > would have to uninstall python 2.4 before alacarte would work. If I get a > chance, I'll work on a solution, but I don't have any python 2.5 boxes at the > moment, so it may take time. Reversing the order of checking Python versions in Alacarte configure.ac file works (done this in 'work' directory). Instead: AM_PATH_PYTHON_VERSION(2.4, 2.4.0, 2.5, 2.5.0) do: AM_PATH_PYTHON_VERSION(2.5, 2.5.0, 2.4, 2.4.0) For python2.4 users nothing would change as configure will this version finally (hope so - haven't tested).
I was planning on generating a patch like that. Have you tested it with both 2.5 and 2.4 on your system? I'll test with just 2.4 before I commit.
(In reply to comment #15) > I was planning on generating a patch like that. Have you tested it with both > 2.5 and 2.4 on your system? I'll test with just 2.4 before I commit. Only 2.5.
Hmm... That's no good, then, because it would have worked without the patch. I need someone to test it with both installed, to make sure it works.
I am also seeing this problem. Notes on my configuration: Processor: PPC Python: 2.4.4 pygtk: 2.10.4 I can attach my config.log if anyone thinks it would help.
I could confirm the same problem here too. checking for pygtk 2.8.0 installed for python 2.4... not found configure: error: required pygtk version not found My system: Python: 2.4.4 pygtk: 2.10.4 I can attach my config.log if anyone thinks it would help. This bug prevets the update of my update to gnome 2.16.13 from 2.16.12.
(In reply to comment #17) > Hmm... That's no good, then, because it would have worked without the patch. I > need someone to test it with both installed, to make sure it works. Sorry I misunderstood you. I hava both 2.4 and 2.5 installed. But 2.4 is almost useless as portage installs every package to currently used version od python 'site-packages' dir. So the patch works with both installed when 2.5 is the main version. I can't check whether it works when both are installed and 2.4 is used. Maybe someone before running python-update script could. Summarizing: it works for me. Both installed. Version 2.5 used.
this problem occured at installed both python-2.4 and 2.5. according to gnome bugzilla, export path to python bin to resolve this. i add 3 lines to ebuild. ># Bug 418871 – Does not compiles with python 2.5 ># http://bugzilla.gnome.org/show_bug.cgi?id=418871 >export PYTHON="`type -p python`" http://palgene-overlay.googlecode.com/svn/new_ebuild/x11-misc/alacarte/
comment #20: No, you have the setup I wanted. I just wanted to make sure that the patch actually worked, and tried 2.5 before 2.4. comment #18 and comment#19 Do you only have python 2.4 installed? If so, post your config.log; if not, you have to use the patch above.
Okay, I've added 0.11.3-r1 with the patch. If you're unmasking python 2.5, you're going to have to live with ~arch alacarte for a bit, I think. Other reporters: If you didn't have python 2.5 installed, please open another bug (because it's a different problem). Make sure to run python-updater no matter what.
(In reply to comment #23) > Okay, I've added 0.11.3-r1 with the patch. If you're unmasking python 2.5, > you're going to have to live with ~arch alacarte for a bit, I think. Something's wrong. When doing 'emerge alacarte' I get: [...] * Applying alacarte-0.11.3-python-2.5.patch ... [ ok ] /usr/portage/x11-misc/alacarte/alacarte-0.11.3-r1.ebuild: line 37: eautoreconf: command not found [...] And the emerging stops at the same point as before. When manually made automake, autoconf, aclocal in 'work' directory configure passed successfully. Maybe wrong command name in ebuild (seems so) - don't know. Haven't done any ebuild stuff yet.
Oops. I've fixed it again. I'm marking this fixed now; if people still have problems with both installed, we can re-open it.
