Re: [eigen] Bitbucket migration

Hi, yes, I've already found this email, and sent him a message on the 6th of September and a reminder on the 17th. But no reply. gael On Wed, Oct 2, 2019 at 11:00 PM Rasmus Munk Larsen wrote: > It looks like the person's work email might be found here: > https://www.ht.sfc.keio.ac.jp/~eigen/

Re: [eigen] Bitbucket migration

It looks like the person's work email might be found here: https://www.ht.sfc.keio.ac.jp/~eigen/ Gael or Christoph, would you consider contacting them directly? On Wed, Oct 2, 2019 at 1:56 PM David Tellenbach < david.tellenb...@tellnotes.org> wrote: > Hi all, > > It also looks like there has

Re: [eigen] Bitbucket migration

Hi all, > It also looks like there has been no activity for 10 months on that account: > > https://gitlab.com/users/eigen/activity > This doesn't seem to be enough: https://about.gitlab.com/support/#dormant-namespace-requests

Re: [eigen] Bitbucket migration

Hi Gael, >> since "eigen" is already taken (and I got no answer from the owner despite one reminder) Have you contacted GitLab support about this? They're usually quite responsive. Eigen is a project with quite some weight behind it, it may not be unlikely that they can do something. -Patrik

Re: [eigen] Bitbucket migration

> This also remind me that we'll have to do something about this git-mirror. We > can either: > (1) - make it empty with a link to the new git repo > (2) - keep it as is (i.e., no sync) for a short period and then proceed as (1) > (3) - delete it and recreate it as a synced mirror of the new

Re: [eigen] Bitbucket migration

On Wed, Sep 18, 2019 at 9:10 AM Christoph Hertzberg < c...@informatik.uni-bremen.de> wrote: > I guess the main decision left is to decide on a schedule when to > officially switch to gitlab and if/how long we will keep the bitbucket > repository as a mirror (or essentially as a snapshot) > What

Re: [eigen] Bitbucket migration

Very nice indeed! Thanks Gael and Joseph! I guess the main decision left is to decide on a schedule when to officially switch to gitlab and if/how long we will keep the bitbucket repository as a mirror (or essentially as a snapshot). Once bitbucket closes hg-support (or sooner), we can replace

Re: [eigen] Bitbucket migration

Wow, very impressive! Thanks, Gael! On Tue, Sep 17, 2019 at 2:31 PM Gael Guennebaud wrote: > > Thanks to Joseph's work, and after fighting with Gitlab.com's super > aggressive spam filter, I finally managed to get the following Gitlab.com > project as a demo of what could be the outcome of a

Re: [eigen] Bitbucket migration

Holy cow this looks impressive! On Tue, Sep 17, 2019 at 2:31 PM Gael Guennebaud wrote: > > Thanks to Joseph's work, and after fighting with Gitlab.com's super > aggressive spam filter, I finally managed to get the following Gitlab.com > project as a demo of what could be the outcome of a full

Re: [eigen] Bitbucket migration

Thanks to Joseph's work, and after fighting with Gitlab.com's super aggressive spam filter, I finally managed to get the following Gitlab.com project as a demo of what could be the outcome of a full migration: https://gitlab.com/ggael/eigen-migration6 This project includes: - a git repo with

Re: [eigen] Bitbucket migration

Dear Eigen, I feel like I've given enough time for someone else to speak up about this but haven't seen this commentary. There is a reason that Eigen hasn't migrated to git earlier and it is also the same reason that there are 6 year old PRs waiting in queue and not closed out or commented on...

Re: [eigen] Bitbucket migration

I added a commit on my fork of fast-export which generate a file with lines as hg_rev_number hg_hash git_hash I pushed it to https://github.com/jmirabel/eigen_tmp/blob/master/hg2git-map Obviously, it should be put in another place. fast-export can also add hg hashes as notes to git commits.

Re: [eigen] Bitbucket migration

Ah sorry, I should have tried that locally myself :) Christoph On 12/09/2019 17.18, Gael Guennebaud wrote: On Thu, Sep 12, 2019 at 4:50 PM Christoph Hertzberg < c...@informatik.uni-bremen.de> wrote: Small question, maybe I'm just missing it: Did you actually translate the 3.x, 2.0 branches

Re: [eigen] Bitbucket migration

On Thu, Sep 12, 2019 at 4:50 PM Christoph Hertzberg < c...@informatik.uni-bremen.de> wrote: > Small question, maybe I'm just missing it: > Did you actually translate the 3.x, 2.0 branches as well or just the > default/master branch? > I just ran the script, and all branches and tags are there,

Re: [eigen] Bitbucket migration

Small question, maybe I'm just missing it: Did you actually translate the 3.x, 2.0 branches as well or just the default/master branch? I'd actually be fine with filtering out all other named branches ... Also, is it possible to apply the tags (from ./.hgtags)? But I agree, great work!

Re: [eigen] Bitbucket migration

Excellent! Thanks a lot! Do you have a hash translation table in some form that I could use in the other scripts? gael On Thu, Sep 12, 2019 at 1:46 PM Joseph Mirabel wrote: > Hello Gael, > > I applied the changes you requested and force-pushed to > github.com/jmirabel/eigen_tmp > > Joseph > >

Re: [eigen] Bitbucket migration

On Thu, Sep 12, 2019 at 9:53 AM Joseph Mirabel wrote: > To summarize what is missing: > > - there are a lot of "backporting rev[0-9]+" that are not found. I don't > know what "backporting" means. I just know that "hg log --rev N" for all > the one I tested returns "unknown revision". > $ hg log

Re: [eigen] Bitbucket migration

On Thu, Sep 12, 2019 at 12:59 AM David Tellenbach < david.tellenb...@tellnotes.org> wrote: > But is it our responsibility to archive such forks? There could be forks > for personal purpose only with no intend to create a PR at all. Should we > really bother to archive these? (At least) everyone

Re: [eigen] Bitbucket migration

To summarize what is missing: - there are a lot of "backporting rev[0-9]+" that are not found. I don't know what "backporting" means. I just know that "hg log --rev N" for all the one I tested returns "unknown revision".   I guess I could fix most of them by adding some of the main developers

Re: [eigen] Bitbucket migration

On 12/09/2019 01.27, Gael Guennebaud wrote: On Wed, Sep 11, 2019 at 6:50 PM Christoph Hertzberg < c...@informatik.uni-bremen.de> wrote: [...] Did we actually plan to migrate bugzilla to gitlab-issues as well? Would we do this by just creating new issues with a link to the bz-archive? (This

Re: [eigen] Bitbucket migration

Hi, > > ** Forks ** > > > > You can see the summary of the fork script there: > > http://manao.inria.fr/eigen_tmp/archive_forks_log.html > > > > > > The hg clones (history+checkout) represents 20GB, maybe 12GB if we remove > > the

Re: [eigen] Bitbucket migration

On Wed, Sep 11, 2019 at 6:50 PM Christoph Hertzberg < c...@informatik.uni-bremen.de> wrote: > > > ** Forks ** > > > > You can see the summary of the fork script there: > > http://manao.inria.fr/eigen_tmp/archive_forks_log.html > > > > The hg clones (history+checkout) represents 20GB, maybe 12GB

Re: [eigen] Bitbucket migration

Dear Eigen developers, First of all, I am not an expert with mercurial and I am fairly good with git. I am in favor of switching to git. I played a bit with fast-export[1]. The changes and same basic usage are on my fork [3]. To see the result, either follow the steps in the README of my fork

Re: [eigen] Bitbucket migration

On 11/09/2019 18.03, Gael Guennebaud wrote: To prepare the migration from bitbucket, I started to play a bit with its API to see what could be done. So far I've quickly draft two (ugly) python scripts to archive the forks and pull-requests. Since this is a one shot for us, I did not cared about