lewis41
2nd August 2010, 08:18 PM
Hello everyone on this forum,
i wish to install F14 using the procedure indicated here:
https://fedoraproject.org/wiki/Releases/Branched#Installing_via_Anaconda
I'm using the F13 DVD, and following the on-screen graphical instructions, i added a mirror repository (e.g. http://fedora.mirror.garr.it/mirrors/fedora/linux/development/14/i386/os), to the repos page of the install wizard but with no connection to the mirror.
The messages are:
"Trying to download" and after some time
"Error:Unable to read package metadata from repository. etc".
The same happens when selecting an update or test repo for F13, so this should be a misconfigured network setting.
A solution is: don't add a new repo, but replace the INSTALL REPO with the mirror from where to download.
With the F13 DVD i've tried passing Anaconda the askmethod boot option; it seems to go:
it configures DHCP but after having downloaded the *.img it stops with a phyton error
The same error happens when trying with a minimal entry in Grub
root (h1,1) the installation partition
kernel /boot//vmlinuz lang=it_IT keymap=it method=http://fedora.mirror.garr.it/mirrors/fedora/linux/development/14/i386/os/ ip=dhcp
initrd /boot/initrd.img
where vmlinuz and initrd.img are F14 files downloaded from repo.
(...)
File "/usr/lib/python2.2/sysconfig.py", line 285, in _init_posix
raise IOError(msg)
IOError: Invalid Python installation: unable to open /usr/include/python2.7/pyconfig-32.h (No such file or directory)
install exited abnormally [1/1].
Has anyone had a similar problem with this type of installation?
Thank you
Luigi
P.S. Ok, perhaps i pretend too much
1. this is my first attempt with a direct network installation
2. F14 is still a pre-pre alpha
(continue)
Yes, the reason is in point 2. of P.S.: the *.img of the phase (1) 2 (?) of anaconda stage has some problem.
Trying to download a *.img for F13 using the DVD with a minimal installer loads the Anaconda graphical interface as requested. So i'll wait ...
Sorry for my excessive anxiousness claim!
i wish to install F14 using the procedure indicated here:
https://fedoraproject.org/wiki/Releases/Branched#Installing_via_Anaconda
I'm using the F13 DVD, and following the on-screen graphical instructions, i added a mirror repository (e.g. http://fedora.mirror.garr.it/mirrors/fedora/linux/development/14/i386/os), to the repos page of the install wizard but with no connection to the mirror.
The messages are:
"Trying to download" and after some time
"Error:Unable to read package metadata from repository. etc".
The same happens when selecting an update or test repo for F13, so this should be a misconfigured network setting.
A solution is: don't add a new repo, but replace the INSTALL REPO with the mirror from where to download.
With the F13 DVD i've tried passing Anaconda the askmethod boot option; it seems to go:
it configures DHCP but after having downloaded the *.img it stops with a phyton error
The same error happens when trying with a minimal entry in Grub
root (h1,1) the installation partition
kernel /boot//vmlinuz lang=it_IT keymap=it method=http://fedora.mirror.garr.it/mirrors/fedora/linux/development/14/i386/os/ ip=dhcp
initrd /boot/initrd.img
where vmlinuz and initrd.img are F14 files downloaded from repo.
(...)
File "/usr/lib/python2.2/sysconfig.py", line 285, in _init_posix
raise IOError(msg)
IOError: Invalid Python installation: unable to open /usr/include/python2.7/pyconfig-32.h (No such file or directory)
install exited abnormally [1/1].
Has anyone had a similar problem with this type of installation?
Thank you
Luigi
P.S. Ok, perhaps i pretend too much
1. this is my first attempt with a direct network installation
2. F14 is still a pre-pre alpha
(continue)
Yes, the reason is in point 2. of P.S.: the *.img of the phase (1) 2 (?) of anaconda stage has some problem.
Trying to download a *.img for F13 using the DVD with a minimal installer loads the Anaconda graphical interface as requested. So i'll wait ...
Sorry for my excessive anxiousness claim!