SCIENTIFIC-LINUX-DEVEL Archives

October 2011

SCIENTIFIC-LINUX-DEVEL@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Maillling list for Scientific Linux developers worldwide <[log in to unmask]>
Date:
Mon, 17 Oct 2011 13:20:56 -0500
Reply-To:
Pat Riehecky <[log in to unmask]>
Content-Transfer-Encoding:
7bit
Content-Type:
text/plain; charset=ISO-8859-1; format=flowed
Subject:
From:
Pat Riehecky <[log in to unmask]>
MIME-Version:
1.0
In-Reply-To:
Organization:
Fermilab
Comments:
To: Jos Vos <[log in to unmask]>
Parts/Attachments:
text/plain (27 lines)
On 10/17/2011 09:28 AM, Jos Vos wrote:
> On Mon, Oct 17, 2011 at 03:41:37PM +0200, Jos Vos wrote:
>
>> It's working again (nothing changed here)!  I tried it again after
>> seeing the messages about the solved problems with rsync.sl.org,
>> and that worked.  So it was related to the state of the SL repo,
>> I think.
> I was too quick... it now fails *during* the install (during or
> just after installing "freetype".
>
> I can now see the full trace, it fails in "mirrorFailureCB".  If you
> want, I can mail a screenshot of the Python traceback.
>

If I could get that screenshot along with a copy of the anaconda log 
that would be great.  I also want to be sure I can replicate the 
environment, so if I could get a sanitized kickstart that would be 
wonderful.  I also want to be sure I'm testing with the same media so if 
I could get an MD5 or SHA1 of your install image that would be great too.

The big ones are the python track and the anaconda logs, that should 
help a lot in diagnosis.

-- 
Pat Riehecky
Scientific Linux Developer

ATOM RSS1 RSS2