Re: invalid END header (bad central directory offset)
Michael Haggerty <[email protected]> Tue, 25 Feb 2014 16:41:27 +0100
| Newsgroups | gmane.comp.version-control.subversion.cvs2svn.user |
|---|---|
| Message-ID | <[email protected]> |
On 02/25/2014 01:49 PM, Edmond Chouaffe wrote: > I just converted a Java project from CVS to GIT, and since then I > receive the following error: error reading commons-logging.jar; invalid > END header (bad central directory offset). > > Does anyone know how to get rid of the error? The most likely cause of your problem is that the file was not marked as binary in CVS. Non-binary files in CVS are subject to end-of-line translation (especially noticeable under Windows) and keyword expansion when they are checked out. Such things will corrupt a JAR file. But before you proceed, please ensure that the file is correct when checked out of CVS. Often people notice corruption after the conversion that was already present before. Then make sure that the file is marked as binary in CVS. This should usually fix the problem. If not, you might want to look at "Prepping your repository" [1] in the docs, "How do I fix up end-of-line translation problems?" [2] in the FAQ, and the file doc/properties.txt [3] in the cvs2svn source tree. Michael [1] http://cvs2svn.tigris.org/cvs2svn.html#prep [2] http://cvs2svn.tigris.org/faq.html#eol-fixup [3] http://cvs2svn.tigris.org/source/browse/cvs2svn/trunk/doc/properties.txt?view=markup -- Michael Haggerty [email protected] http://softwareswirl.blogspot.com/ ------------------------------------------------------ http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=3073588 To unsubscribe from this discussion, e-mail: [[email protected]].