Re: [DISCUSS] Correct converted GIT repo(s) from SVN - earlier (Re: [VOTE][RESULT] Moving SCM to Git)

[Svante Schubert <sv...@gmail.com>]

Just a short heads-up on the ongoing svn2git transformation:

I was able to create one of the two desired git repositories from our SVN
repository with git version 2.14.2.windows.3 on Windows 10 via
https://git-scm.com/docs/git-svn
saving the remote author file from https://git-wip-us.apache.org/authors.txt
locally aside.

   1. First repo, our website: https://svn.apache.
   org/repos/asf/incubator/odf/site/
   <https://svn.apache.org/repos/asf/incubator/odf/site/>
   via the command "git svn clone https://svn.apache.org/repos/
   asf/incubator/odf/site -T trunk -t tags -A authors.txt"
   You may the result find on: https://github.com/
   svanteschubert/odftoolkit-site
   NOTE: We should add a README with the information from
   http://incubator.apache.org/odftoolkit/website-local.html
   <http://incubator.apache.org/odftoolkit/website-local.html>
   after we agreed on the outcome.
   2. Second repo, our main repo from https://svn.apache.org/repos/
   asf/incubator/odf/ is still ongoing.
   The direct transformation via the command "git svn clone
   https://svn.apache.org/repos/asf/incubator/odf
   <https://svn.apache.org/repos/asf/incubator/odf> -T trunk -t tags -A
   authors.txt" failed first.
   As "devinhan" also appeared earlier as "devin" and could not be found in
   the "author.txt" and the execution stopped overnight. After duplicating
   Devin's entry according to his previous ID in the local "authors.txt", it
   worked and had about half a dozen connect problems overnight (the latter
   using Linux) and local svn repo was not accepted.
   Therefore, I am trying now to simplify and clone the SVN repo via:
      1. svnrdump dump https://svn.apache.org/repos/asf/incubator/odf/trunk
      > source-repo.dump
      2. svnadmin create /path/to/repository
      3. svnadmin load /path/to/repository < svnexport.dump


But if this fails again, I am pretty sure, I will suggest using the
existing git repo form: https://github.com/apache/odftoolkit
and the website from https://github.com/svanteschubert/odftoolkit-site

You may already take a look at the git repos from github if you notice some
problems and/or further todos before we hand them over to Infra:

https://github.com/svanteschubert/odftoolkit-site
For instance, a README is missing, for instance with the website handling.

And the existing project repo:
https://github.com/apache/odftoolkit

What do you think?

Cheers,
Svante



2017-09-25 19:09 GMT+02:00 Svante Schubert <sv...@gmail.com>:

> I have been told, that the team of Apache Infrastructure has no way to
> verify the correctness of change history after a conversion from SVN to GIT
> is done.
> Therefore, the community (we on this list) should do the SVN to GIT
> conversion ourselves and should agree on the outcome.
>
> So, let me start to suggest to review the existing Apache GitHub
> repository of our 'trunk' for correctness: https://github.com/apache/odft
> oolkit
> You might check out the sources via command line using: git clone
> https://github.com/apache/odftoolkit.git
>
> Still, three questions come to my mind:
>
>    1. What kind of additional improvements could we think of aside from
>    what the Apache GitHub mirror <https://github.com/apache/odftoolkit>
>    is offering? Michael mentioned some quality criteria
>    <https://lists.apache.org/thread.html/d02741ed7c0bc4f0a6d010489611c7803413d495509ad99b906ce754@%3Codf-dev.incubator.apache.org%3E>
>    before.
>    2. Yet, the second repository, the one for our website is missing. Is
>    there any volunteer to provide some initial transformation and the steps
>    that led to the result?
>    3. If we would like to push the results to Infra and exchange them to
>    test among us, how do we do this?
>    I suggest we exchange them by cloning the repositories from/to our
>    personal GitHub accounts.
>
> Cheers,
> Svante
>
> PS: The info from Greg (Infra Admin) below:
>
> The Infra team has no way to verify a svn->git converted
>> repository. That is something for the community to perform. And once they
>> are satisfied with their conversion, then to push the result to their new
>> git repository.
>> "if you have a lot of history", then that's actually where we're
>> really unable to help. The more history, the less we could possibly know
>> what the community wants.
>> To clarify: it is expected that the community performs the svn->git
>> conversion, examine/verify the result, repeat until acceptable. The Infra
>> team just doesn't have the community knowledge to perform the
>> verification.
>> Per [1], we describe the procedure:
>> "Please use reporeq <https://reporeq.apache.org/> to create your intended
>> Git repo(s). Run svn2git locally using this authors file
>> <https://git-wip-us.apache.org/authors.txt> and push once the conversion
>> result is confirmed. File an INFRA ticket to mark your SVN repository
>> readonly. Optionally, file a ticket to temporarily disable commit emails
>> for when you push your converted clone."
>>
>> If there are any questions about the procedure, then an email to
>> users@infra.a.o is the best, first stop.
>> Cheers,
>> Greg Stein
>> Infrastructure Administrator, ASF
>> [1] https://www.apache.org/dev/infra-contact
>
>
>
> 2017-09-25 12:44 GMT+02:00 Svante Schubert <sv...@gmail.com>:
>
>> Hi Everyone,
>>
>> Git has been voted unanimous as new SCM with 8 votes including at least 3
>> committer / PPMC members.
>>
>> The vote thread can be found at:
>> https://lists.apache.org/thread.html/e4cd8594d32b593ac5607f9
>> 4eff431cfd66e6548d7eac2906f5f2248@%3Codf-dev.incubator.apache.org%3E
>>
>> I’ll file an INFRA ticket to begin the process. I assume they will
>> leave SVN up, but make it read-only and then create our Git
>> repo from whatever tip/head of SVN they start from.
>>
>> Cheers,
>> Svante
>>
>> ᐧ
>>
>
> ᐧ
>

ᐧ