Gramps-3.1.1 fails to emerege. There are at least 2 problems: 1. It fails to find pygtk 2. It may fail to recognize python-2.6 in some cases. The error for #1 (from the emerge output) is: ... preceeding configure output ... checking for python version... 2.6 checking for python platform... linux2 checking for python script directory... ${prefix}/lib/python2.6/site-packages checking for python extension module directory... ${exec_prefix}/lib/python2.6/site-packages checking for sh... /bin/sh checking Python bindings for gtk 2.10 (pygtk2>=2.10.0)... configure: error: **** The python bindings for gtk 2.10 (pygtk2>=2.10.0) could not be found. Error #2 may not be a "hard" error, since the unmodified configure seems to find python2.6, but the code is wrong in that line 6456 om the configure file says: for am_cv_pathless_PYTHON in python python2 python2.5 python2.4... is missing python2.6. However adding this and rerunning configure does not fix the gtk problem. Reproducible: Always Steps to Reproduce: 1. emerge gramps Actual Results: It cannot emerge due to a failure to find pygtk (or misidentifies the version). Expected Results: The configure should work and it should emerge properly. After identification of the gtk problem, I re-emerged pygtk-2.14.1. It properly put the updated gtk libraries in /usr/lib/python2.6/site-packages/gtk-2.0. However, it did not create /usr/lib/python2.6/site-packages/pygtk.pth and pygtk.py and the files they point to. Instead it recreated the symbolic links in /usr/lib/python2.5/site-packages! So there is a problem with emerging pygtk not getting its installation process straight -- it puts the binaries in the right place but it updates their locations in the previous version files. (Very strange). Even after I put the correct files into /usr/lib/python2.6/site-packages emerging gramps still could not find pygtk2>=2.10.0 -- so there is still something wrong with the configure file in its attempt to locate where pygtk is or how to varify its version.
Created attachment 191226 [details] config.log from gramps emerge attempt Shows the problem finding the python bindings for gtk 2.10 (pygtk>=2.10.0).
And yes, before you ask, python-updater has been run. Whether it worked completely or not I do not know. It takes 3+ hours to run and produces a 6.6 megabyte (~67,000 line) output file (which I'm not about to review).
Please provide the environment file (see the end of emerge's output).
Ok, gramps will finally emerge. The trick was to get pygtk properly installed with python2.6. As noted in other bugs, my attempt to install pygtk led to a situation where the python2.6/gtk-2.0 files were properly updated but the top level gtk files that point to the gtk-2.0 directory were placed in /usr/lib/python2.5. This was fixed by copying the files and symlinks into the /usr/lib/python2.6 directory. As a side note, python-updater gives seems to give no indications with respect to all of the "old" python "site-packages" which need to be re-installed following a python upgrade (I still haven't found all I suspect are required on my system -- the number is probably 20+ packages). The portage/python packages should keep track of all packages installed into python#.#/site-packages and inform the user of the need for re-emerges when python is upgraded. It would be nice if this were "optional" (kind of like etc-update) since the user may not want to "move forward" all old packages due to the disk space consumption. There should also be a way to delete old python version packages as one becomes more confident in the stability of the new python version.
Changed status to FIXED. Perhaps there should be some "OTHER PACKAGE" option indicative of the problem being resolved in another package (in this case pygtk) to indicate that gramps is not at fault. I would still note that the configure file needs to be patched to include python2.6 in the list of python versions it scans in an attempt to find python on systems where it cannot be identified by more "standard" means.
