Re: after recent update, svn tools exiting with code 57
Dave Steenburgh wrote: I haven't been able to find any info related to this problem; hopefully someone can point me in the right direction. From time to time, I use setup.exe to update all the packages I have installed. After doing that earlier today, I found out that svn, svnadmin, and svnserve (and presumably all other svn tools) are exiting with code 57 and no error message, with complete disregard for command-line options. Assuming this is a propogation of a Windows error: $ net helpmsg 57 A network adapter hardware error occurred. Any chance? -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: after recent update, svn tools exiting with code 57
On 12/31/2008 10:33 AM, Dave Steenburgh wrote: From time to time, I use setup.exe to update all the packages I have installed. After doing that earlier today, I found out that svn, svnadmin, and svnserve (and presumably all other svn tools) are exiting with code 57 and no error message, with complete disregard for command-line options. I currently have version 1.5.5-1 installed. I tried reverting to 1.5.4-1, and got the same results, so I'm assuming the problem is one of the other packages that got updated. Naturally, I don't know which packages got updated, nor do I know which packages svn depends on. Nothing else has given me any trouble yet. Try downgrading libapr1 and libaprutil1. I recently rebuilt these packages for Cygwin 1.7, but it appears they were accidently put in the Cygwin 1.5 release area. You want the -1 versions. -- David Rothenberger daver...@acm.org God is a comedian playing to an audience too afraid to laugh. -- Voltaire -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: after recent update, svn tools exiting with code 57
On Wed, Dec 31, 2008 at 2:19 PM, Larry Hall (Cygwin) reply-to-list-only...@cygwin.com wrote: Dave Steenburgh wrote: I haven't been able to find any info related to this problem; hopefully someone can point me in the right direction. From time to time, I use setup.exe to update all the packages I have installed. After doing that earlier today, I found out that svn, svnadmin, and svnserve (and presumably all other svn tools) are exiting with code 57 and no error message, with complete disregard for command-line options. Assuming this is a propogation of a Windows error: $ net helpmsg 57 A network adapter hardware error occurred. Any chance? Well, my network adapter isn't perfect, but it works fine 99.99% of the time. Even so, since the same exit code results even with --version or --help, I don't think the network adapter is to blame. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: after recent update, svn tools exiting with code 57
On Wed, Dec 31, 2008 at 2:45 PM, David Rothenberger daver...@acm.org wrote: On 12/31/2008 10:33 AM, Dave Steenburgh wrote: From time to time, I use setup.exe to update all the packages I have installed. After doing that earlier today, I found out that svn, svnadmin, and svnserve (and presumably all other svn tools) are exiting with code 57 and no error message, with complete disregard for command-line options. I currently have version 1.5.5-1 installed. I tried reverting to 1.5.4-1, and got the same results, so I'm assuming the problem is one of the other packages that got updated. Naturally, I don't know which packages got updated, nor do I know which packages svn depends on. Nothing else has given me any trouble yet. Try downgrading libapr1 and libaprutil1. I recently rebuilt these packages for Cygwin 1.7, but it appears they were accidently put in the Cygwin 1.5 release area. You want the -1 versions. Thanks! It works fine now. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/