On Mon, Dec 6, 2010 at 6:45 PM, Ashish Verma <ilugid@xxxxxxxxx> wrote:
Your answers.file need to contain the strings identically the same as
you would enter them interactively in one line for each answer.I did that...Each on one line. no space nothing... still it accepted only
the first one and then skipped the rest.
HTH
-- Arun Khan
I now downloaded the the tcl and tk packages and tried to install them,
however since gcc was missing, got the compiler errors. When I tried to yum
install gcc, I got the below yum checksum errors. I checked the repomd.xml
file on the server and saw it contained the correct sha256 sum of the
primary_db file that was downloaded. However I was still getting this error.
I found the below link for the same. I cant change the version of sha that
the repo was created with. How can I go around this kind of issue. Is there
a way I can make the python script run sha256 instead of whatever it is
currently running on my system.
Ref Link
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
http://prefetch.net/blog/index.php/2009/11/26/dealing-with-yum-checksum-errors/
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
ERROR
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
http://download.fedora.redhat.com/pub/fedora/linux/releases/12/Everything/i386/os/repodata/01a9150327554e6d65132266f7b065a5d107b4efb7afa78012fa3ffcc6f517e9-primary.sqlite.bz2:
[Errno -3] Error performing checksum
Error: failure:
repodata/01a9150327554e6d65132266f7b065a5d107b4efb7afa78012fa3ffcc6f517e9-primary.sqlite.bz2
from avfedora: [Errno 256] No more mirrors to try.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
Though I can create my own repo and get around this issue. I would like to
know how to solve the below error for future ref.
Regards,
Ashish
