Re: [Help-gnu-arch] Help composing a sample session
Thomas Lord <[email protected]> Wed, 09 Jan 2008 20:22:35 -0800
| Newsgroups | gmane.comp.version-control.arch.user |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --===============0614544005== Content-Type: multipart/alternative; boundary="------------080302040804030305080203" This is a multi-part message in MIME format. --------------080302040804030305080203 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I dunno. If you want to track it down and find out what's really going on it should be easy to grep for the error message, run tla under gdb, set some breakpoints, and figure out how you got there (if not apparent from static inspection). I mean I know you know you can do all that -- I'm just adding the information that, at this late date, that's probably your best bet, sadly. A guess? I dunno. Perhaps its bitrot. Andy has been quite gracefully and generously maintaining the grounds of Arch but they have, more or less, long lain fallow, afaict. Sorry you're finding troubles with it but it's (with all due respect to Andy and his caretaking) largely a long-dead project. -t Eric S. Raymond wrote: > Thomas Lord <[email protected]>: > >> As I recall, a valid log file is vaguely RFC822-ish in the sense that >> it has headers, then a line with nothing but a newline, then a body. >> > > I don't think that's the problem, then. Logfile attached. > > ------------------------------------------------------------------------ > > Summary: First commit > Keywords: > > This is a dummy commit message. > --------------080302040804030305080203 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> I dunno. If you want to track it down and find out what's really going on it should be easy to grep for the error message, run tla under gdb, set some breakpoints, and figure out how you got there (if not apparent from static inspection). I mean I know you know you can do all that -- I'm just adding the information that, at this late date, that's probably your best bet, sadly.<br> <br> A guess? I dunno. Perhaps its bitrot. Andy has been quite gracefully and generously maintaining the grounds of Arch but they have, more or less, long lain fallow, afaict. Sorry you're finding troubles with it but it's (with all due respect to Andy and his caretaking) largely a long-dead project.<br> <br> -t<br> <br> <br> <br> Eric S. Raymond wrote: <blockquote cite="[email protected]" type="cite"> <pre wrap="">Thomas Lord <a class="moz-txt-link-rfc2396E" href="mailto:[email protected]"><[email protected]></a>: </pre> <blockquote type="cite"> <pre wrap="">As I recall, a valid log file is vaguely RFC822-ish in the sense that it has headers, then a line with nothing but a newline, then a body. </pre> </blockquote> <pre wrap=""><!----> I don't think that's the problem, then. Logfile attached. </pre> <pre wrap=""> <hr size="4" width="90%"> Summary: First commit Keywords: This is a dummy commit message. </pre> </blockquote> <br> </body> </html> --------------080302040804030305080203-- --===============0614544005== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline