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

Open
GoogleCodeExporter opened this Issue Mar 17, 2015 · 14 comments

Comments

Projects
None yet
7 participants
@GoogleCodeExporter
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

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 17, 2015

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

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

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 17, 2015

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

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

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 17, 2015

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

  • Changed state: Accepted
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

  • Changed state: Accepted
@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 17, 2015

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:

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

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 17, 2015

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

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

@MarcusWolschon

This comment has been minimized.

Show comment
Hide comment
@MarcusWolschon

MarcusWolschon Mar 18, 2015

We have the same issue with https://code.google.com/p/osmeditor4android/
The repository totals at 34.8 MB, so there couldn't possibly be a 100+MB file in there.
I got reports from other people with the same issue and also repositories <100MB.

We have the same issue with https://code.google.com/p/osmeditor4android/
The repository totals at 34.8 MB, so there couldn't possibly be a 100+MB file in there.
I got reports from other people with the same issue and also repositories <100MB.

@tobson

This comment has been minimized.

Show comment
Hide comment
@tobson

tobson Mar 18, 2015

Same here: https://code.google.com/p/pencil-code/

On Wed, Mar 18, 2015 at 12:46 PM, Marcus Wolschon notifications@github.com
wrote:

We have the same issue with https://code.google.com/p/osmeditor4android/
(a total of 34.8 MB in the repository)


Reply to this email directly or view it on GitHub
#16 (comment)
.

tobson commented Mar 18, 2015

Same here: https://code.google.com/p/pencil-code/

On Wed, Mar 18, 2015 at 12:46 PM, Marcus Wolschon notifications@github.com
wrote:

We have the same issue with https://code.google.com/p/osmeditor4android/
(a total of 34.8 MB in the repository)


Reply to this email directly or view it on GitHub
#16 (comment)
.

@MarcusWolschon

This comment has been minimized.

Show comment
Hide comment
@MarcusWolschon

MarcusWolschon Mar 20, 2015

Issue still exists. Still can't migrate the project.

Issue still exists. Still can't migrate the project.

@MarcusWolschon

This comment has been minimized.

Show comment
Hide comment
@MarcusWolschon

MarcusWolschon Mar 25, 2015

Aparently something was fixed earlier this week but nobody cared to update the issue tracker to tell anyone about it.

Aparently something was fixed earlier this week but nobody cared to update the issue tracker to tell anyone about it.

@JimBacon

This comment has been minimized.

Show comment
Hide comment
@JimBacon

JimBacon Jul 28, 2015

I experienced this failure message so deleted my new repository and tried the import again. It failed three or four times at different percentage-completion but finally made it to the end... I think. I saw it go from 99% import to 30% optimising to no message but a green icon looking a bit like certificate with a ribbon. The promised email on completion is yet to arrive.
import-complete-maybe

I experienced this failure message so deleted my new repository and tried the import again. It failed three or four times at different percentage-completion but finally made it to the end... I think. I saw it go from 99% import to 30% optimising to no message but a green icon looking a bit like certificate with a ribbon. The promised email on completion is yet to arrive.
import-complete-maybe

@niemyjski

This comment has been minimized.

Show comment
Hide comment
@niemyjski

niemyjski Jul 30, 2015

I'm seeing this as well.

I'm seeing this as well.

@JimBacon

This comment has been minimized.

Show comment
Hide comment
@JimBacon

JimBacon Jul 31, 2015

I got the email to say my import was successful in the end. It got hung up in our anti-spam system for a while. I've done several more imports since and my conclusion is that the green certificate indicates successful completion.
It would be really helpful if the text were updated from "We're importing commits..." to "Import completed successfully."

I got the email to say my import was successful in the end. It got hung up in our anti-spam system for a while. I've done several more imports since and my conclusion is that the green certificate indicates successful completion.
It would be really helpful if the text were updated from "We're importing commits..." to "Import completed successfully."

@iFreilicht

This comment has been minimized.

Show comment
Hide comment
@iFreilicht

iFreilicht Apr 11, 2016

Workaround in case anyone still has this problem: http://stackoverflow.com/a/16330439/2533467

Workaround in case anyone still has this problem: http://stackoverflow.com/a/16330439/2533467

@frekele

This comment has been minimized.

Show comment
Hide comment
@frekele

frekele May 15, 2016

Solution for me:

The problem is the size of a file, which cannot exceed 100M.

Before migrating to github, in the repository do this:

git clone --mirror git://example.com/some-big-repo.git

wget http://repo1.maven.org/maven2/com/madgag/bfg/1.12.12/bfg-1.12.12.jar

mv bfg-1.12.12.jar bfg.jar

java -jar bfg.jar --strip-blobs-bigger-than 100M some-big-repo.git

cd some-big-repo.git

git reflog expire --expire=now --all && git gc --prune=now --aggressive

git push

Ready!

Now make the migration again by the tool: https://github.com/new/import

see more:
http://stackoverflow.com/questions/22227851/error-while-pushing-to-github-repo
and
https://rtyley.github.io/bfg-repo-cleaner/

I hope I helped you. :)

frekele commented May 15, 2016

Solution for me:

The problem is the size of a file, which cannot exceed 100M.

Before migrating to github, in the repository do this:

git clone --mirror git://example.com/some-big-repo.git

wget http://repo1.maven.org/maven2/com/madgag/bfg/1.12.12/bfg-1.12.12.jar

mv bfg-1.12.12.jar bfg.jar

java -jar bfg.jar --strip-blobs-bigger-than 100M some-big-repo.git

cd some-big-repo.git

git reflog expire --expire=now --all && git gc --prune=now --aggressive

git push

Ready!

Now make the migration again by the tool: https://github.com/new/import

see more:
http://stackoverflow.com/questions/22227851/error-while-pushing-to-github-repo
and
https://rtyley.github.io/bfg-repo-cleaner/

I hope I helped you. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment