Mirroring repository to Git
Issue #62
resolved
Since Bitbucket will drop Mercurial support starting from 1st June, 2020 (see: https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket), the repository must be mirrored to Git or moved to some other Mercurial VC hosting service.
Comments (21)
-
-
Ha-ha! :)) In “How to migrate and export“ section they provide a link to alternative hosting site list (https://www.mercurial-scm.org/wiki/MercurialHosting) and include themselves as a “Historical site“ there:
Bitbucket: Offered Mercurial hosting until 2020-05-31, before going Git-only. -
- changed status to on hold
-
reporter
This is the OGRE migration post-mortem: http://www.yosoygames.com.ar/wp/2019/09/migrating-repos-from-mercurial-to-git/ They migrated from Bitbucket+Mercurial to GitHub+Git few weeks ago. If you’re interested, I can introduce you to one of their lead developer who took care of the migration process.
-
Thank you, Raffaele. That was a very useful reading.
-
reporter
- changed status to open
Hey @Oleh Derevenko , any news on this topic? (I've reopened the issue just to get some visibility)
-
Yes, I’ve tested migration tools guys suggested and we seem to be OK (check the repository I added under my account for preview). When I’ll have a convenient moment I’ll migrate the main ODE repository. We still have time till the end of the May.
-
reporter
Cool! No problem, I’m not in hurry. Just wanted to be sure that this issue hadn’t been forgotten.
-
we just migrated osrf/gazebo to GitHub using https://github.com/philipstarkey/bitbucket-hg-exporter and https://github.com/frej/fast-export, which imported the issues directly into GitHub issues and archived the pull request discussions on a GitHub pages site:
- https://bitbucket.org/osrf/gazebo
- https://github.com/osrf/gazebo
- https://osrf-migration.github.io/gazebo-gh-pages/#!/osrf/gazebo/pull-requests/page/1
let me know if you have any questions; I'd be happy to advise on how we ran the export
-
I guess we’ll stay here, at Bitbucket. No reason to make another relocation and create yet another place where the ODE is hosted. It’s also more work that can be avoided. Thank you for your offer, though. I’ll keep it in mind if there’ll be any problems here I’ll not be able to overcome.
-
check the repository I added under my account for preview
can you add a link? bitbucket has obscured user names, so I don't know how to find this
-
ok, I think I found it: https://bitbucket.org/oleh-derevenko/ode-test1/src/master/
-
are you planning to archive the old issues or pull requests?
-
I suppose the issues will be preserved as they are. And regarding the pull requests, we don't have any useful of them.
-
I was assuming that the issues and pull requests would be deleted along with the mercurial repository, so I would recommend a plan for migrating them. I believe you can export the issues from the site settings interface and then import them in the new git repository.
-
I believe issues are related to a project, not to a repository. One project can have several repositories.
-
oh, I was under the impression that the following issues will be deleted on June 1st if some additional action is not taken
just to be safe, I would recommend using the issue exporter after you've stopped using this repo and directed people to the new one
-
Don't worry, Steve. These issues are of little value. What can be fixed is fixed quickly. All the other issues will never be done. The project has no developers.
-
- changed status to resolved
-
it looks like you have migrated this repository to git and renamed the old one to ode-hg:
and you've managed to keep the issues, which I think is great!
the pull request history will be lost, but that may be of less concern to you
-
@Steve Peters
I used Export and Import as you suggested. Thank you. - Log in to comment
Yes, I know this. We will discuss the situation on the mail group and make a decision later.