search

sjlae / support-tools

Automatically exported from code.google.com/p/support-tools
Apache License 2.0
0 stars 0 forks source link

GitHub import fails with "There was an error importing commits" #16

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
Attempt to export https://code.google.com/p/ftpii/ to 
https://github.com/joedj/ftpii/

What is the expected output? What do you see instead?
Expected output is a successful project import.
Observed output is "There was an error importing commits" at 
https://import.github.com/joedj/ftpii/import

Original issue reported on code.google.com by joe.goo...@psychlaw.com.au on 13 Mar 2015 at 2:29

GoogleCodeExporter commented 9 years ago 
Thank you for the bug report. That particular error indicates the problem was 
with the GitHub importer. I'll forward on your project's information. I'll 
update this bug as soon as the issue gets resolved.

If you are a hurry to migrate your project, you can manually export your 
project using our guide here:
https://code.google.com/p/support-tools/wiki/MigratingToGitHub

Original comment by chrsm...@google.com on 13 Mar 2015 at 2:33

GoogleCodeExporter commented 9 years ago 
I'm seeing that as well: https://import.github.com/spookypeanut/t7gre/import. 
I'm guessing there will be more: could you put contact details for who to send 
the info to in here for anyone else that sees this please?

Original comment by spookypeanut on 13 Mar 2015 at 11:02

GoogleCodeExporter commented 9 years ago 
I'm still working on updating our documentation and error messages here, but it 
appears that one of the most common sources of this error is that GitHub has a 
100MB restriction on the size of individual files. So it is possible to have a 
Google Code repo containing files larger than 100MB, but those will fail to 
import into GitHub.

You can push your repository to GitHub if you *obliterate* any offending files 
from your repo. (But a simple `git rm` will not work.)

IF you delete the file in a single commit, the large file is still in your 
repository's history. And therefore will still fail when importing a prior 
commit. For git-based projects you can use the steps outlined in GitHub's 
[https://help.github.com/articles/remove-sensitive-data/ removing sensitive 
data] article, which will walk you though how to remove a file from a repos 
history entirely.

As for hg and svn-based projects, I still need to track down how you can remove 
any offending files before the GitHub import.

Original comment by chrsm...@google.com on 14 Mar 2015 at 10:56

GoogleCodeExporter commented 9 years ago 
In the case of https://code.google.com/p/ftpii/ there has never been a 100MB 
file in the SVN repository.  The repository size has never exceeded 10MB.

I've attached a script that others may find useful to check for this - note 
that it looks at the size of the repo, not individual files.

Original comment by joe.jor...@gmail.com on 14 Mar 2015 at 12:32

Attachments:

GoogleCodeExporter commented 9 years ago 
I have an SVN repo that I do have a file larger than 100 MB in, that is causing 
this error. Please update this ticket if you find a way to remove this from the 
history so I can finish my migration.

Original comment by ris...@gmail.com on 15 Mar 2015 at 12:05