Created attachment 435923 [details] screenshot of anaconda traceback Description of problem: It is currently impossible to install Branched due to anaconda not being able to find pyconfig-32.h. I tried to install a kvm guest on an F-13 host.
I see the same problem on x86_64 except missing pyconfig-64.h. ----- Running anaconda 14.12, the Fedora system installer - please wait. Traceack (most recent call last): File "/usr/lib64/phthon2.7/site.py", line 553, in <module> main() File "/usr/lib64/python2.7/site.py", line 535, in main known_paths = addusersitepackages(known_paths) File "/usr/lib64/python2.7/site.py:, line 264", in addusersitepackages user_site = getusersitepackages() File "/usr/lib64/pytohon2.7/site.py", line 239, in getusersitepackages user_base = getuserbase() # this will also set USER_BASE File "/usr/lib64/python2.7/site.py", line 229, in getuserbase USER_BASE = get_config_var('userbase') File "/usr/lib64/python2.7/sysconfig.py", line 518, in get_config_var return get_config_vars().get(name) File "/usr/lib64/python2.7/sysconfig.py", line 421, in get_config_vars _init_posix(_CONFIG_VARS) File "/usr/lib64/python2.7/sysconfig.py", line 285, in _init_posix raise IOError(msg) IOError: invalid Python installation: unable to open /usr/include/python2.7/pyconfig-64.h (No such file or directory) install exited abnormally [1/1] -----
Created attachment 435946 [details] /tmp/anaconda.log
Reproduced here too.
*** Bug 620297 has been marked as a duplicate of this bug. ***
I have the same problem with it.
Strange issue. We had similar problems, when rebuilding anything with python 2.7, but I thought this was fixed in python 2.7-4. What python version is currently on the F-14 Alpha?
python-2.7-7.fc14 on both DVDs.
$ repoquery -f /usr/include/python2.7/pyconfig-32.h --repoid=rawhide --enablerepo=rawhide python-0:2.7-7.fc14.i686 $ repoquery -f /usr/include/python2.7/pyconfig-64.h --repoid=rawhide --enablerepo=rawhide python-0:2.7-7.fc14.x86_64 Hmm, should be there.
http://git.fedorahosted.org/git/?p=anaconda.git;a=commit;h=f821da35d32098e855709a6b83a95ccebeca99d2 Isn't that fixed in git already? Maybe all we need is a new anaconda release.
*** Bug 620354 has been marked as a duplicate of this bug. ***
Yes, that's all that needs to be done.
clumens: Are you expecting a newer anaconda build, or should we just need to use the existing anaconda-13.14-1 koji build?
Can we have a build for F-14 please?
You could always try looking in koji: http://koji.fedoraproject.org/koji/buildinfo?buildID=187810
oops, missed that somehow. sorry for the noise.
Note that https://admin.fedoraproject.org/updates/anaconda-14.14-1.fc14 is awaiting testing. I'm not sure exactly what the build process is for the installer. As I understand it, the install.img needs to be built with anaconda-14.14-1 or later for it to work.
*** Bug 620464 has been marked as a duplicate of this bug. ***
No longer seeing the reported problem when testing with anaconda-14.14-1 using test compose#2 - http://serverbeach1.fedoraproject.org/pub/alt/stage/14.TC2/ NOTE: You will run into bug#620900 using TC2
Is there any ETA when the fixed install.img will make it to "normal" mirrors?
(In reply to comment #19) > Is there any ETA when the fixed install.img will make it to "normal" mirrors? Test composes are not published to mirrors. Please use the URL in comment#18 for any downloads. Closing this issue since it is resolved in test compose#2 (anaconda-14.14-1)