Re: Apache Lucene/Solr GIT migration, requesting infra help

[Shalin Shekhar Mangar]

Got it, thanks! I'll try your suggestion, Dawid.

On Sat, Jan 23, 2016 at 2:36 PM, Dawid Weiss  wrote:
> If you're using github then yes, you will need to fork again and
> rebase any changes you may have. This can be done by having two
> origins locally (two "sources" of commits) -- one from the old clone,
> the second one from the new clone. Then you can rebase the branches or
> commits you wish and push them to the new clone.
>
> Dawid
>
>
> On Sat, Jan 23, 2016 at 9:55 AM, Daniel Gruno  wrote:
>> On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
>>> Thanks Dawid and Daniel for all the work!
>>>
>>> One strange thing that I noticed is that my fork of apache/lucene-solr
>>> at https://github.com/shalinmangar/lucene-solr is now shown to be a
>>> fork of https://github.com/mdodsworth/lucene-solr. I have no idea who
>>> that guy is. What can we do to fix this?
>>
>> Nothing. This is GitHub's fallback method when the original repository
>> goes away as it did here (replaced with a new repo with a new history).
>> Since referring to the old repo which doesn't exist anymore would break
>> your copy, they have fallen back to another copy of it.
>>
>> Please re-fork.
>>
>> With regards,
>> Daniel.
>>
>>>
>>> On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss  wrote:
 1. The content of the lucene-solr.git repository looks good!

 2) PROBLEM. I can't push my own branch:

 $ git co master -b git-check
 $ [... committed a dummy commit ]
 $ git push origin HEAD -u
 fatal: remote error: access denied or repository not exported: 
 /lucene-solr.git

 3) Solr repo is still available for some reason, both as real git repo 
 here:

 git://git.apache.org/solr.git

 and listed here:

 https://git.apache.org/

 Could I be seeing a mirror or something?

 Dawid


 On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss  wrote:
> Checking everything now -- that was fast Daniel!
> Dawid
>
>
> On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  
> wrote:
>> Just a heads up: Everything is working now and GitHub has caught up with
>> the new repository. You should be good to go :)
>>
>> With regards,
>> Daniel.
>>
>> On 01/23/2016 08:36 AM, Daniel Gruno wrote:
>>> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
 Hello Daniel,

 I've prepared everything for the migration and I hand it off to you (I
 will be available in the morning, if you need assistance). I can also
 log on to hipchat, but send me an e-mail if you wish me to.

 Here are the steps we kindly ask you to perform (I allowed myself to
 uppercase certain things, apologies if it looks like shouting):

 1) Permanently REMOVE the following git mirrors of SVN (reason: they
 are obsolete and incorrect syncs, consolidated git repo contains full
 history):

 git://git.apache.org/solr.git
>>> DONE
>>>
 git://git.apache.org/lucene.git
>>> DONE

 2) Notify (somehow) GitHub that these two repos have been removed
 (they should not be available or visible on GitHub as well):

 https://github.com/apache/lucene
>>> DONE
 https://github.com/apache/solr
>>> DONE
>>>

 3) DISABLE svn syncing for the following git mirror:

 git://git.apache.org/lucene-solr.git
>>> DONE
>>>

 and then REPLACE it (wipe it clean) with the content of the following
 consolidated repository:

 g...@github.com:dweiss/lucene-solr-svn2git.git

 I don't know how it looks from the backend's side, but this should
 also work, if there are sufficient permissions:

 git clone g...@github.com:dweiss/lucene-solr-svn2git.git
 git remote add apache git://git.apache.org/lucene-solr.git
 git push --mirror apache
>>> We have our own methods, but nonetheless DONE. Please check that you
>>> have write-access to the new repo.

 4) I don't know if we need to make GitHub aware of the replaced
 content of the lucene-solr repo or if their syncing will handle this
 automatically. It would be nice if they could catch up as quickly as
 possible.
>>>
>>> As explained on the JIRA ticket, if we're lucky, this should happen
>>> automagically in about 20 minutes from now. If not, we'll have to wait
>>> 24 hours. Time will tell :)
>>>
>>> With regards,
>>> Daniel.
>>>

 In case of questions, problems or a successful import, please drop me
 an e-mail. Oh, thank you for being so nice and helping us on your day
 off -- much appreciated.

 Dawid

Re: Apache Lucene/Solr GIT migration, requesting infra help

[Dawid Weiss]

1. The content of the lucene-solr.git repository looks good!

2) PROBLEM. I can't push my own branch:

$ git co master -b git-check
$ [... committed a dummy commit ]
$ git push origin HEAD -u
fatal: remote error: access denied or repository not exported: /lucene-solr.git

3) Solr repo is still available for some reason, both as real git repo here:

git://git.apache.org/solr.git

and listed here:

https://git.apache.org/

Could I be seeing a mirror or something?

Dawid


On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss  wrote:
> Checking everything now -- that was fast Daniel!
> Dawid
>
>
> On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  wrote:
>> Just a heads up: Everything is working now and GitHub has caught up with
>> the new repository. You should be good to go :)
>>
>> With regards,
>> Daniel.
>>
>> On 01/23/2016 08:36 AM, Daniel Gruno wrote:
>>> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
 Hello Daniel,

 I've prepared everything for the migration and I hand it off to you (I
 will be available in the morning, if you need assistance). I can also
 log on to hipchat, but send me an e-mail if you wish me to.

 Here are the steps we kindly ask you to perform (I allowed myself to
 uppercase certain things, apologies if it looks like shouting):

 1) Permanently REMOVE the following git mirrors of SVN (reason: they
 are obsolete and incorrect syncs, consolidated git repo contains full
 history):

 git://git.apache.org/solr.git
>>> DONE
>>>
 git://git.apache.org/lucene.git
>>> DONE

 2) Notify (somehow) GitHub that these two repos have been removed
 (they should not be available or visible on GitHub as well):

 https://github.com/apache/lucene
>>> DONE
 https://github.com/apache/solr
>>> DONE
>>>

 3) DISABLE svn syncing for the following git mirror:

 git://git.apache.org/lucene-solr.git
>>> DONE
>>>

 and then REPLACE it (wipe it clean) with the content of the following
 consolidated repository:

 g...@github.com:dweiss/lucene-solr-svn2git.git

 I don't know how it looks from the backend's side, but this should
 also work, if there are sufficient permissions:

 git clone g...@github.com:dweiss/lucene-solr-svn2git.git
 git remote add apache git://git.apache.org/lucene-solr.git
 git push --mirror apache
>>> We have our own methods, but nonetheless DONE. Please check that you
>>> have write-access to the new repo.

 4) I don't know if we need to make GitHub aware of the replaced
 content of the lucene-solr repo or if their syncing will handle this
 automatically. It would be nice if they could catch up as quickly as
 possible.
>>>
>>> As explained on the JIRA ticket, if we're lucky, this should happen
>>> automagically in about 20 minutes from now. If not, we'll have to wait
>>> 24 hours. Time will tell :)
>>>
>>> With regards,
>>> Daniel.
>>>

 In case of questions, problems or a successful import, please drop me
 an e-mail. Oh, thank you for being so nice and helping us on your day
 off -- much appreciated.

 Dawid

>>>
>>

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Apache Lucene/Solr GIT migration, requesting infra help

[Daniel Gruno]

Just a heads up: Everything is working now and GitHub has caught up with
the new repository. You should be good to go :)

With regards,
Daniel.

On 01/23/2016 08:36 AM, Daniel Gruno wrote:
> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
>> Hello Daniel,
>>
>> I've prepared everything for the migration and I hand it off to you (I
>> will be available in the morning, if you need assistance). I can also
>> log on to hipchat, but send me an e-mail if you wish me to.
>>
>> Here are the steps we kindly ask you to perform (I allowed myself to
>> uppercase certain things, apologies if it looks like shouting):
>>
>> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
>> are obsolete and incorrect syncs, consolidated git repo contains full
>> history):
>>
>> git://git.apache.org/solr.git
> DONE
> 
>> git://git.apache.org/lucene.git
> DONE
>>
>> 2) Notify (somehow) GitHub that these two repos have been removed
>> (they should not be available or visible on GitHub as well):
>>
>> https://github.com/apache/lucene
> DONE
>> https://github.com/apache/solr
> DONE
> 
>>
>> 3) DISABLE svn syncing for the following git mirror:
>>
>> git://git.apache.org/lucene-solr.git
> DONE
> 
>>
>> and then REPLACE it (wipe it clean) with the content of the following
>> consolidated repository:
>>
>> g...@github.com:dweiss/lucene-solr-svn2git.git
>>
>> I don't know how it looks from the backend's side, but this should
>> also work, if there are sufficient permissions:
>>
>> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
>> git remote add apache git://git.apache.org/lucene-solr.git
>> git push --mirror apache
> We have our own methods, but nonetheless DONE. Please check that you
> have write-access to the new repo.
>>
>> 4) I don't know if we need to make GitHub aware of the replaced
>> content of the lucene-solr repo or if their syncing will handle this
>> automatically. It would be nice if they could catch up as quickly as
>> possible.
> 
> As explained on the JIRA ticket, if we're lucky, this should happen
> automagically in about 20 minutes from now. If not, we'll have to wait
> 24 hours. Time will tell :)
> 
> With regards,
> Daniel.
> 
>>
>> In case of questions, problems or a successful import, please drop me
>> an e-mail. Oh, thank you for being so nice and helping us on your day
>> off -- much appreciated.
>>
>> Dawid
>>
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Apache Lucene/Solr GIT migration, requesting infra help

[Dawid Weiss]

Checking everything now -- that was fast Daniel!
Dawid


On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  wrote:
> Just a heads up: Everything is working now and GitHub has caught up with
> the new repository. You should be good to go :)
>
> With regards,
> Daniel.
>
> On 01/23/2016 08:36 AM, Daniel Gruno wrote:
>> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
>>> Hello Daniel,
>>>
>>> I've prepared everything for the migration and I hand it off to you (I
>>> will be available in the morning, if you need assistance). I can also
>>> log on to hipchat, but send me an e-mail if you wish me to.
>>>
>>> Here are the steps we kindly ask you to perform (I allowed myself to
>>> uppercase certain things, apologies if it looks like shouting):
>>>
>>> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
>>> are obsolete and incorrect syncs, consolidated git repo contains full
>>> history):
>>>
>>> git://git.apache.org/solr.git
>> DONE
>>
>>> git://git.apache.org/lucene.git
>> DONE
>>>
>>> 2) Notify (somehow) GitHub that these two repos have been removed
>>> (they should not be available or visible on GitHub as well):
>>>
>>> https://github.com/apache/lucene
>> DONE
>>> https://github.com/apache/solr
>> DONE
>>
>>>
>>> 3) DISABLE svn syncing for the following git mirror:
>>>
>>> git://git.apache.org/lucene-solr.git
>> DONE
>>
>>>
>>> and then REPLACE it (wipe it clean) with the content of the following
>>> consolidated repository:
>>>
>>> g...@github.com:dweiss/lucene-solr-svn2git.git
>>>
>>> I don't know how it looks from the backend's side, but this should
>>> also work, if there are sufficient permissions:
>>>
>>> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
>>> git remote add apache git://git.apache.org/lucene-solr.git
>>> git push --mirror apache
>> We have our own methods, but nonetheless DONE. Please check that you
>> have write-access to the new repo.
>>>
>>> 4) I don't know if we need to make GitHub aware of the replaced
>>> content of the lucene-solr repo or if their syncing will handle this
>>> automatically. It would be nice if they could catch up as quickly as
>>> possible.
>>
>> As explained on the JIRA ticket, if we're lucky, this should happen
>> automagically in about 20 minutes from now. If not, we'll have to wait
>> 24 hours. Time will tell :)
>>
>> With regards,
>> Daniel.
>>
>>>
>>> In case of questions, problems or a successful import, please drop me
>>> an e-mail. Oh, thank you for being so nice and helping us on your day
>>> off -- much appreciated.
>>>
>>> Dawid
>>>
>>
>

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Apache Lucene/Solr GIT migration, requesting infra help

[Daniel Gruno]

On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
> Thanks Dawid and Daniel for all the work!
> 
> One strange thing that I noticed is that my fork of apache/lucene-solr
> at https://github.com/shalinmangar/lucene-solr is now shown to be a
> fork of https://github.com/mdodsworth/lucene-solr. I have no idea who
> that guy is. What can we do to fix this?

Nothing. This is GitHub's fallback method when the original repository
goes away as it did here (replaced with a new repo with a new history).
Since referring to the old repo which doesn't exist anymore would break
your copy, they have fallen back to another copy of it.

Please re-fork.

With regards,
Daniel.

> 
> On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss  wrote:
>> 1. The content of the lucene-solr.git repository looks good!
>>
>> 2) PROBLEM. I can't push my own branch:
>>
>> $ git co master -b git-check
>> $ [... committed a dummy commit ]
>> $ git push origin HEAD -u
>> fatal: remote error: access denied or repository not exported: 
>> /lucene-solr.git
>>
>> 3) Solr repo is still available for some reason, both as real git repo here:
>>
>> git://git.apache.org/solr.git
>>
>> and listed here:
>>
>> https://git.apache.org/
>>
>> Could I be seeing a mirror or something?
>>
>> Dawid
>>
>>
>> On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss  wrote:
>>> Checking everything now -- that was fast Daniel!
>>> Dawid
>>>
>>>
>>> On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  wrote:
 Just a heads up: Everything is working now and GitHub has caught up with
 the new repository. You should be good to go :)

 With regards,
 Daniel.

 On 01/23/2016 08:36 AM, Daniel Gruno wrote:
> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
>> Hello Daniel,
>>
>> I've prepared everything for the migration and I hand it off to you (I
>> will be available in the morning, if you need assistance). I can also
>> log on to hipchat, but send me an e-mail if you wish me to.
>>
>> Here are the steps we kindly ask you to perform (I allowed myself to
>> uppercase certain things, apologies if it looks like shouting):
>>
>> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
>> are obsolete and incorrect syncs, consolidated git repo contains full
>> history):
>>
>> git://git.apache.org/solr.git
> DONE
>
>> git://git.apache.org/lucene.git
> DONE
>>
>> 2) Notify (somehow) GitHub that these two repos have been removed
>> (they should not be available or visible on GitHub as well):
>>
>> https://github.com/apache/lucene
> DONE
>> https://github.com/apache/solr
> DONE
>
>>
>> 3) DISABLE svn syncing for the following git mirror:
>>
>> git://git.apache.org/lucene-solr.git
> DONE
>
>>
>> and then REPLACE it (wipe it clean) with the content of the following
>> consolidated repository:
>>
>> g...@github.com:dweiss/lucene-solr-svn2git.git
>>
>> I don't know how it looks from the backend's side, but this should
>> also work, if there are sufficient permissions:
>>
>> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
>> git remote add apache git://git.apache.org/lucene-solr.git
>> git push --mirror apache
> We have our own methods, but nonetheless DONE. Please check that you
> have write-access to the new repo.
>>
>> 4) I don't know if we need to make GitHub aware of the replaced
>> content of the lucene-solr repo or if their syncing will handle this
>> automatically. It would be nice if they could catch up as quickly as
>> possible.
>
> As explained on the JIRA ticket, if we're lucky, this should happen
> automagically in about 20 minutes from now. If not, we'll have to wait
> 24 hours. Time will tell :)
>
> With regards,
> Daniel.
>
>>
>> In case of questions, problems or a successful import, please drop me
>> an e-mail. Oh, thank you for being so nice and helping us on your day
>> off -- much appreciated.
>>
>> Dawid
>>
>

>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
> 
> 
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Apache Lucene/Solr GIT migration, requesting infra help

[Shalin Shekhar Mangar]

Thanks Dawid and Daniel for all the work!

One strange thing that I noticed is that my fork of apache/lucene-solr
at https://github.com/shalinmangar/lucene-solr is now shown to be a
fork of https://github.com/mdodsworth/lucene-solr. I have no idea who
that guy is. What can we do to fix this?

On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss  wrote:
> 1. The content of the lucene-solr.git repository looks good!
>
> 2) PROBLEM. I can't push my own branch:
>
> $ git co master -b git-check
> $ [... committed a dummy commit ]
> $ git push origin HEAD -u
> fatal: remote error: access denied or repository not exported: 
> /lucene-solr.git
>
> 3) Solr repo is still available for some reason, both as real git repo here:
>
> git://git.apache.org/solr.git
>
> and listed here:
>
> https://git.apache.org/
>
> Could I be seeing a mirror or something?
>
> Dawid
>
>
> On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss  wrote:
>> Checking everything now -- that was fast Daniel!
>> Dawid
>>
>>
>> On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  wrote:
>>> Just a heads up: Everything is working now and GitHub has caught up with
>>> the new repository. You should be good to go :)
>>>
>>> With regards,
>>> Daniel.
>>>
>>> On 01/23/2016 08:36 AM, Daniel Gruno wrote:
 On 01/23/2016 03:02 AM, Dawid Weiss wrote:
> Hello Daniel,
>
> I've prepared everything for the migration and I hand it off to you (I
> will be available in the morning, if you need assistance). I can also
> log on to hipchat, but send me an e-mail if you wish me to.
>
> Here are the steps we kindly ask you to perform (I allowed myself to
> uppercase certain things, apologies if it looks like shouting):
>
> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
> are obsolete and incorrect syncs, consolidated git repo contains full
> history):
>
> git://git.apache.org/solr.git
 DONE

> git://git.apache.org/lucene.git
 DONE
>
> 2) Notify (somehow) GitHub that these two repos have been removed
> (they should not be available or visible on GitHub as well):
>
> https://github.com/apache/lucene
 DONE
> https://github.com/apache/solr
 DONE

>
> 3) DISABLE svn syncing for the following git mirror:
>
> git://git.apache.org/lucene-solr.git
 DONE

>
> and then REPLACE it (wipe it clean) with the content of the following
> consolidated repository:
>
> g...@github.com:dweiss/lucene-solr-svn2git.git
>
> I don't know how it looks from the backend's side, but this should
> also work, if there are sufficient permissions:
>
> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
> git remote add apache git://git.apache.org/lucene-solr.git
> git push --mirror apache
 We have our own methods, but nonetheless DONE. Please check that you
 have write-access to the new repo.
>
> 4) I don't know if we need to make GitHub aware of the replaced
> content of the lucene-solr repo or if their syncing will handle this
> automatically. It would be nice if they could catch up as quickly as
> possible.

 As explained on the JIRA ticket, if we're lucky, this should happen
 automagically in about 20 minutes from now. If not, we'll have to wait
 24 hours. Time will tell :)

 With regards,
 Daniel.

>
> In case of questions, problems or a successful import, please drop me
> an e-mail. Oh, thank you for being so nice and helping us on your day
> off -- much appreciated.
>
> Dawid
>

>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>



-- 
Regards,
Shalin Shekhar Mangar.

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Apache Lucene/Solr GIT migration, requesting infra help

[Dawid Weiss]

If you're using github then yes, you will need to fork again and
rebase any changes you may have. This can be done by having two
origins locally (two "sources" of commits) -- one from the old clone,
the second one from the new clone. Then you can rebase the branches or
commits you wish and push them to the new clone.

Dawid


On Sat, Jan 23, 2016 at 9:55 AM, Daniel Gruno  wrote:
> On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
>> Thanks Dawid and Daniel for all the work!
>>
>> One strange thing that I noticed is that my fork of apache/lucene-solr
>> at https://github.com/shalinmangar/lucene-solr is now shown to be a
>> fork of https://github.com/mdodsworth/lucene-solr. I have no idea who
>> that guy is. What can we do to fix this?
>
> Nothing. This is GitHub's fallback method when the original repository
> goes away as it did here (replaced with a new repo with a new history).
> Since referring to the old repo which doesn't exist anymore would break
> your copy, they have fallen back to another copy of it.
>
> Please re-fork.
>
> With regards,
> Daniel.
>
>>
>> On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss  wrote:
>>> 1. The content of the lucene-solr.git repository looks good!
>>>
>>> 2) PROBLEM. I can't push my own branch:
>>>
>>> $ git co master -b git-check
>>> $ [... committed a dummy commit ]
>>> $ git push origin HEAD -u
>>> fatal: remote error: access denied or repository not exported: 
>>> /lucene-solr.git
>>>
>>> 3) Solr repo is still available for some reason, both as real git repo here:
>>>
>>> git://git.apache.org/solr.git
>>>
>>> and listed here:
>>>
>>> https://git.apache.org/
>>>
>>> Could I be seeing a mirror or something?
>>>
>>> Dawid
>>>
>>>
>>> On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss  wrote:
 Checking everything now -- that was fast Daniel!
 Dawid


 On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  wrote:
> Just a heads up: Everything is working now and GitHub has caught up with
> the new repository. You should be good to go :)
>
> With regards,
> Daniel.
>
> On 01/23/2016 08:36 AM, Daniel Gruno wrote:
>> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
>>> Hello Daniel,
>>>
>>> I've prepared everything for the migration and I hand it off to you (I
>>> will be available in the morning, if you need assistance). I can also
>>> log on to hipchat, but send me an e-mail if you wish me to.
>>>
>>> Here are the steps we kindly ask you to perform (I allowed myself to
>>> uppercase certain things, apologies if it looks like shouting):
>>>
>>> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
>>> are obsolete and incorrect syncs, consolidated git repo contains full
>>> history):
>>>
>>> git://git.apache.org/solr.git
>> DONE
>>
>>> git://git.apache.org/lucene.git
>> DONE
>>>
>>> 2) Notify (somehow) GitHub that these two repos have been removed
>>> (they should not be available or visible on GitHub as well):
>>>
>>> https://github.com/apache/lucene
>> DONE
>>> https://github.com/apache/solr
>> DONE
>>
>>>
>>> 3) DISABLE svn syncing for the following git mirror:
>>>
>>> git://git.apache.org/lucene-solr.git
>> DONE
>>
>>>
>>> and then REPLACE it (wipe it clean) with the content of the following
>>> consolidated repository:
>>>
>>> g...@github.com:dweiss/lucene-solr-svn2git.git
>>>
>>> I don't know how it looks from the backend's side, but this should
>>> also work, if there are sufficient permissions:
>>>
>>> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
>>> git remote add apache git://git.apache.org/lucene-solr.git
>>> git push --mirror apache
>> We have our own methods, but nonetheless DONE. Please check that you
>> have write-access to the new repo.
>>>
>>> 4) I don't know if we need to make GitHub aware of the replaced
>>> content of the lucene-solr repo or if their syncing will handle this
>>> automatically. It would be nice if they could catch up as quickly as
>>> possible.
>>
>> As explained on the JIRA ticket, if we're lucky, this should happen
>> automagically in about 20 minutes from now. If not, we'll have to wait
>> 24 hours. Time will tell :)
>>
>> With regards,
>> Daniel.
>>
>>>
>>> In case of questions, problems or a successful import, please drop me
>>> an e-mail. Oh, thank you for being so nice and helping us on your day
>>> off -- much appreciated.
>>>
>>> Dawid
>>>
>>
>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>>
>>
>>
>>
>
>
> 

Re: Apache Lucene/Solr GIT migration, requesting infra help

[Michael McCandless]

Thank you Dawid and Daniel for all the hard work here!!

Mike McCandless

http://blog.mikemccandless.com


On Sat, Jan 23, 2016 at 4:21 AM, Shalin Shekhar Mangar
 wrote:
> Got it, thanks! I'll try your suggestion, Dawid.
>
> On Sat, Jan 23, 2016 at 2:36 PM, Dawid Weiss  wrote:
>> If you're using github then yes, you will need to fork again and
>> rebase any changes you may have. This can be done by having two
>> origins locally (two "sources" of commits) -- one from the old clone,
>> the second one from the new clone. Then you can rebase the branches or
>> commits you wish and push them to the new clone.
>>
>> Dawid
>>
>>
>> On Sat, Jan 23, 2016 at 9:55 AM, Daniel Gruno  wrote:
>>> On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
 Thanks Dawid and Daniel for all the work!

 One strange thing that I noticed is that my fork of apache/lucene-solr
 at https://github.com/shalinmangar/lucene-solr is now shown to be a
 fork of https://github.com/mdodsworth/lucene-solr. I have no idea who
 that guy is. What can we do to fix this?
>>>
>>> Nothing. This is GitHub's fallback method when the original repository
>>> goes away as it did here (replaced with a new repo with a new history).
>>> Since referring to the old repo which doesn't exist anymore would break
>>> your copy, they have fallen back to another copy of it.
>>>
>>> Please re-fork.
>>>
>>> With regards,
>>> Daniel.
>>>

 On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss  wrote:
> 1. The content of the lucene-solr.git repository looks good!
>
> 2) PROBLEM. I can't push my own branch:
>
> $ git co master -b git-check
> $ [... committed a dummy commit ]
> $ git push origin HEAD -u
> fatal: remote error: access denied or repository not exported: 
> /lucene-solr.git
>
> 3) Solr repo is still available for some reason, both as real git repo 
> here:
>
> git://git.apache.org/solr.git
>
> and listed here:
>
> https://git.apache.org/
>
> Could I be seeing a mirror or something?
>
> Dawid
>
>
> On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss  
> wrote:
>> Checking everything now -- that was fast Daniel!
>> Dawid
>>
>>
>> On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  
>> wrote:
>>> Just a heads up: Everything is working now and GitHub has caught up with
>>> the new repository. You should be good to go :)
>>>
>>> With regards,
>>> Daniel.
>>>
>>> On 01/23/2016 08:36 AM, Daniel Gruno wrote:
 On 01/23/2016 03:02 AM, Dawid Weiss wrote:
> Hello Daniel,
>
> I've prepared everything for the migration and I hand it off to you (I
> will be available in the morning, if you need assistance). I can also
> log on to hipchat, but send me an e-mail if you wish me to.
>
> Here are the steps we kindly ask you to perform (I allowed myself to
> uppercase certain things, apologies if it looks like shouting):
>
> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
> are obsolete and incorrect syncs, consolidated git repo contains full
> history):
>
> git://git.apache.org/solr.git
 DONE

> git://git.apache.org/lucene.git
 DONE
>
> 2) Notify (somehow) GitHub that these two repos have been removed
> (they should not be available or visible on GitHub as well):
>
> https://github.com/apache/lucene
 DONE
> https://github.com/apache/solr
 DONE

>
> 3) DISABLE svn syncing for the following git mirror:
>
> git://git.apache.org/lucene-solr.git
 DONE

>
> and then REPLACE it (wipe it clean) with the content of the following
> consolidated repository:
>
> g...@github.com:dweiss/lucene-solr-svn2git.git
>
> I don't know how it looks from the backend's side, but this should
> also work, if there are sufficient permissions:
>
> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
> git remote add apache git://git.apache.org/lucene-solr.git
> git push --mirror apache
 We have our own methods, but nonetheless DONE. Please check that you
 have write-access to the new repo.
>
> 4) I don't know if we need to make GitHub aware of the replaced
> content of the lucene-solr repo or if their syncing will handle this
> automatically. It would be nice if they could catch up as quickly as
> possible.

 As explained on the JIRA ticket, if we're lucky, this should happen
 automagically in about 20 minutes from now. If not, we'll have to wait

Re: Apache Lucene/Solr GIT migration, requesting infra help

[Steve Rowe]

Thanks Dawid and Daniel!

--
Steve
www.lucidworks.com

> On Jan 23, 2016, at 3:45 PM, Erick Erickson  wrote:
> 
> Indeed, thanks for your work Dawid and Daniel!!
> 
> On Sat, Jan 23, 2016 at 1:34 AM, Michael McCandless
>  wrote:
>> Thank you Dawid and Daniel for all the hard work here!!
>> 
>> Mike McCandless
>> 
>> http://blog.mikemccandless.com
>> 
>> 
>> On Sat, Jan 23, 2016 at 4:21 AM, Shalin Shekhar Mangar
>>  wrote:
>>> Got it, thanks! I'll try your suggestion, Dawid.
>>> 
>>> On Sat, Jan 23, 2016 at 2:36 PM, Dawid Weiss  wrote:
 If you're using github then yes, you will need to fork again and
 rebase any changes you may have. This can be done by having two
 origins locally (two "sources" of commits) -- one from the old clone,
 the second one from the new clone. Then you can rebase the branches or
 commits you wish and push them to the new clone.
 
 Dawid
 
 
 On Sat, Jan 23, 2016 at 9:55 AM, Daniel Gruno  wrote:
> On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
>> Thanks Dawid and Daniel for all the work!
>> 
>> One strange thing that I noticed is that my fork of apache/lucene-solr
>> at https://github.com/shalinmangar/lucene-solr is now shown to be a
>> fork of https://github.com/mdodsworth/lucene-solr. I have no idea who
>> that guy is. What can we do to fix this?
> 
> Nothing. This is GitHub's fallback method when the original repository
> goes away as it did here (replaced with a new repo with a new history).
> Since referring to the old repo which doesn't exist anymore would break
> your copy, they have fallen back to another copy of it.
> 
> Please re-fork.
> 
> With regards,
> Daniel.
> 
>> 
>> On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss  
>> wrote:
>>> 1. The content of the lucene-solr.git repository looks good!
>>> 
>>> 2) PROBLEM. I can't push my own branch:
>>> 
>>> $ git co master -b git-check
>>> $ [... committed a dummy commit ]
>>> $ git push origin HEAD -u
>>> fatal: remote error: access denied or repository not exported: 
>>> /lucene-solr.git
>>> 
>>> 3) Solr repo is still available for some reason, both as real git repo 
>>> here:
>>> 
>>> git://git.apache.org/solr.git
>>> 
>>> and listed here:
>>> 
>>> https://git.apache.org/
>>> 
>>> Could I be seeing a mirror or something?
>>> 
>>> Dawid
>>> 
>>> 
>>> On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss  
>>> wrote:
 Checking everything now -- that was fast Daniel!
 Dawid
 
 
 On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  
 wrote:
> Just a heads up: Everything is working now and GitHub has caught up 
> with
> the new repository. You should be good to go :)
> 
> With regards,
> Daniel.
> 
> On 01/23/2016 08:36 AM, Daniel Gruno wrote:
>> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
>>> Hello Daniel,
>>> 
>>> I've prepared everything for the migration and I hand it off to you 
>>> (I
>>> will be available in the morning, if you need assistance). I can 
>>> also
>>> log on to hipchat, but send me an e-mail if you wish me to.
>>> 
>>> Here are the steps we kindly ask you to perform (I allowed myself to
>>> uppercase certain things, apologies if it looks like shouting):
>>> 
>>> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
>>> are obsolete and incorrect syncs, consolidated git repo contains 
>>> full
>>> history):
>>> 
>>> git://git.apache.org/solr.git
>> DONE
>> 
>>> git://git.apache.org/lucene.git
>> DONE
>>> 
>>> 2) Notify (somehow) GitHub that these two repos have been removed
>>> (they should not be available or visible on GitHub as well):
>>> 
>>> https://github.com/apache/lucene
>> DONE
>>> https://github.com/apache/solr
>> DONE
>> 
>>> 
>>> 3) DISABLE svn syncing for the following git mirror:
>>> 
>>> git://git.apache.org/lucene-solr.git
>> DONE
>> 
>>> 
>>> and then REPLACE it (wipe it clean) with the content of the 
>>> following
>>> consolidated repository:
>>> 
>>> g...@github.com:dweiss/lucene-solr-svn2git.git
>>> 
>>> I don't know how it looks from the backend's side, but this should
>>> also work, if there are sufficient permissions:
>>> 
>>> git clone g...@github.com:dweiss/lucene-solr-svn2git.git

RE: Apache Lucene/Solr GIT migration, requesting infra help

[Uwe Schindler]

Hi,

 

Github is just a mirror, as before. We don’t do our development on Github, but 
people can do it there in forks of Githubs mirror. New code changes must always 
be pushed by committers to the git-wip-us.apache.org server with their 
apache.org user name.

 

The official read-only GIT URL is: git://git.apache.org/lucene-solr.git

The Jenkins servers are configured to use this URL.

 

Uwe

 

-

Uwe Schindler

H.-H.-Meier-Allee 63, D-28213 Bremen

 <http://www.thetaphi.de/> http://www.thetaphi.de

eMail: u...@thetaphi.de

 

From: Jack Krupansky [mailto:jack.krupan...@gmail.com] 
Sent: Saturday, January 23, 2016 10:38 PM
To: Lucene-dev <dev@lucene.apache.org>
Subject: Re: Apache Lucene/Solr GIT migration, requesting infra help

 

The tiniest of nits: Could somebody update the Lucene and Solr web pages for 
the location of source code:

https://lucene.apache.org/core/developer.html

http://lucene.apache.org/solr/resources.html

 

Just to confirm, this really is the primary copy of the Lucene/Solr source code 
now, right?

https://github.com/apache/lucene-solr

 

Well, technically that seems to still be a mirror of whatever the actually repo 
really is... is this the absolute primary copy, here?

https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git

 

I'm just wondering exactly which URL should be used to view the (definitive) 
current source, especially since I know in the past there were issues with the 
github mirror being behind svn. But is this new "mirror" truly only a mirror or 
is it now the real repo? I do see that if I click on the links in the git 
commit notifications they have some funky old format, not the more modern 
github formatting.

 

As an example, if I want to view the definitive source for the tagged release 
for 5.4.1, is the official repo here:

https://github.com/apache/lucene-solr/tree/releases/lucene-solr/5.4.1

or

https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;a=commit;h=f54d853a3c3a2ddcf24ee7e2c837dc4d403bc0b0

(That's the page I get if I click on the releases/lucene-solr/5.4.1 link on the 
ASF Cananonical Repository icon for Lucene-Solr.)

 

And finally, is the old commit notifications mailing list relevant anymore, or 
should people be encouraged to enable watching of the github repository? I 
noticed that (of course) I am not currently watching the new github repo 
(mirror), but am getting notifications - is there some magic involved or are 
github commit notifications automatically sent to the dev list? (ahh... I do 
see that the sender of the github commit info actually is still 
comm...@lucene.apache.org <mailto:comm...@lucene.apache.org> , so clearly the 
commit notification list is being used.) Is that intentional for the long run 
or just an expedient for the transition until people get familiar with github?

 

I am reasonably familiar with github, but git behind the Apache firewall is 
still somewhat a mystery. A few more clues about what is really going on would 
be helpful. Or at least stuff average contributors might care about, not the 
hard-core Infra stuff.

 

Thanks.




-- Jack Krupansky

 

On Sat, Jan 23, 2016 at 3:45 PM, Erick Erickson <erickerick...@gmail.com 
<mailto:erickerick...@gmail.com> > wrote:

Indeed, thanks for your work Dawid and Daniel!!


On Sat, Jan 23, 2016 at 1:34 AM, Michael McCandless
<luc...@mikemccandless.com <mailto:luc...@mikemccandless.com> > wrote:
> Thank you Dawid and Daniel for all the hard work here!!
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Sat, Jan 23, 2016 at 4:21 AM, Shalin Shekhar Mangar
> <shalinman...@gmail.com <mailto:shalinman...@gmail.com> > wrote:
>> Got it, thanks! I'll try your suggestion, Dawid.
>>
>> On Sat, Jan 23, 2016 at 2:36 PM, Dawid Weiss <dawid.we...@gmail.com 
>> <mailto:dawid.we...@gmail.com> > wrote:
>>> If you're using github then yes, you will need to fork again and
>>> rebase any changes you may have. This can be done by having two
>>> origins locally (two "sources" of commits) -- one from the old clone,
>>> the second one from the new clone. Then you can rebase the branches or
>>> commits you wish and push them to the new clone.
>>>
>>> Dawid
>>>
>>>
>>> On Sat, Jan 23, 2016 at 9:55 AM, Daniel Gruno <humbed...@apache.org 
>>> <mailto:humbed...@apache.org> > wrote:
>>>> On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
>>>>> Thanks Dawid and Daniel for all the work!
>>>>>
>>>>> One strange thing that I noticed is that my fork of apache/lucene-solr
>>>>> at https://github.com/shalinmangar/lucene-solr is now shown to be a
>>>>> fork of https://github.com/mdodsworth/lucene-solr. I have no idea who

Re: Apache Lucene/Solr GIT migration, requesting infra help

[Jack Krupansky]

The tiniest of nits: Could somebody update the Lucene and Solr web pages
for the location of source code:
https://lucene.apache.org/core/developer.html
http://lucene.apache.org/solr/resources.html

Just to confirm, this really is the primary copy of the Lucene/Solr source
code now, right?
https://github.com/apache/lucene-solr

Well, technically that seems to still be a mirror of whatever the actually
repo really is... is this the absolute primary copy, here?
https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git

I'm just wondering exactly which URL should be used to view the
(definitive) current source, especially since I know in the past there were
issues with the github mirror being behind svn. But is this new "mirror"
truly only a mirror or is it now the real repo? I do see that if I click on
the links in the git commit notifications they have some funky old format,
not the more modern github formatting.

As an example, if I want to view the definitive source for the tagged
release for 5.4.1, is the official repo here:
https://github.com/apache/lucene-solr/tree/releases/lucene-solr/5.4.1
or
https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;a=commit;h=f54d853a3c3a2ddcf24ee7e2c837dc4d403bc0b0
(That's the page I get if I click on the releases/lucene-solr/5.4.1 link on
the ASF Cananonical Repository icon for Lucene-Solr.)

And finally, is the old commit notifications mailing list relevant anymore,
or should people be encouraged to enable watching of the github repository?
I noticed that (of course) I am not currently watching the new github repo
(mirror), but am getting notifications - is there some magic involved or
are github commit notifications automatically sent to the dev list? (ahh...
I do see that the sender of the github commit info actually is still
comm...@lucene.apache.org, so clearly the commit notification list is being
used.) Is that intentional for the long run or just an expedient for the
transition until people get familiar with github?

I am reasonably familiar with github, but git behind the Apache firewall is
still somewhat a mystery. A few more clues about what is really going on
would be helpful. Or at least stuff average contributors might care about,
not the hard-core Infra stuff.

Thanks.

-- Jack Krupansky

On Sat, Jan 23, 2016 at 3:45 PM, Erick Erickson 
wrote:

> Indeed, thanks for your work Dawid and Daniel!!
>
> On Sat, Jan 23, 2016 at 1:34 AM, Michael McCandless
>  wrote:
> > Thank you Dawid and Daniel for all the hard work here!!
> >
> > Mike McCandless
> >
> > http://blog.mikemccandless.com
> >
> >
> > On Sat, Jan 23, 2016 at 4:21 AM, Shalin Shekhar Mangar
> >  wrote:
> >> Got it, thanks! I'll try your suggestion, Dawid.
> >>
> >> On Sat, Jan 23, 2016 at 2:36 PM, Dawid Weiss 
> wrote:
> >>> If you're using github then yes, you will need to fork again and
> >>> rebase any changes you may have. This can be done by having two
> >>> origins locally (two "sources" of commits) -- one from the old clone,
> >>> the second one from the new clone. Then you can rebase the branches or
> >>> commits you wish and push them to the new clone.
> >>>
> >>> Dawid
> >>>
> >>>
> >>> On Sat, Jan 23, 2016 at 9:55 AM, Daniel Gruno 
> wrote:
>  On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
> > Thanks Dawid and Daniel for all the work!
> >
> > One strange thing that I noticed is that my fork of
> apache/lucene-solr
> > at https://github.com/shalinmangar/lucene-solr is now shown to be a
> > fork of https://github.com/mdodsworth/lucene-solr. I have no idea
> who
> > that guy is. What can we do to fix this?
> 
>  Nothing. This is GitHub's fallback method when the original repository
>  goes away as it did here (replaced with a new repo with a new
> history).
>  Since referring to the old repo which doesn't exist anymore would
> break
>  your copy, they have fallen back to another copy of it.
> 
>  Please re-fork.
> 
>  With regards,
>  Daniel.
> 
> >
> > On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss 
> wrote:
> >> 1. The content of the lucene-solr.git repository looks good!
> >>
> >> 2) PROBLEM. I can't push my own branch:
> >>
> >> $ git co master -b git-check
> >> $ [... committed a dummy commit ]
> >> $ git push origin HEAD -u
> >> fatal: remote error: access denied or repository not exported:
> /lucene-solr.git
> >>
> >> 3) Solr repo is still available for some reason, both as real git
> repo here:
> >>
> >> git://git.apache.org/solr.git
> >>
> >> and listed here:
> >>
> >> https://git.apache.org/
> >>
> >> Could I be seeing a mirror or something?
> >>
> >> Dawid
> >>
> >>
> >> On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss 
> wrote:
> >>> 

Re: Apache Lucene/Solr GIT migration, requesting infra help

[Dawid Weiss]

> It is a bit stupid that the last commit in SVN was just reverted and not made 
> completely hidden. I would have synced up the converted repo only up to the 
> revision before the final *delete all* commit instead of reverting it.

I did this intentionally. This way SVN history and git history don't
have any gaps -- they're a seamless transition from one to the other.

The two commits... well, yes - true, they could be avoided. The
repository can stay as it is, no need to rewrite anything. You could
just change the position of references (branch_5x and master) and
branch them off before the wipeout commit, then force-push them. At
this point this would mean people's local master/branch_5x branches
would be diverged from history, so they'd have to update.

I don't think it's worth the hassle, to be honest.

Dawid

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Apache Lucene/Solr GIT migration, requesting infra help

[Anshum Gupta]

Thanks Dawid and Daniel for all the effort!

On Sat, Jan 23, 2016 at 2:40 PM, Dawid Weiss  wrote:

> > is the official repo here:
> > https://github.com/apache/lucene-solr/tree/releases/lucene-solr/5.4.1
> > or
> >
> https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;a=commit;h=f54d853a3c3a2ddcf24ee7e2c837dc4d403bc0b0
>
> With git it does not technically matter which the "official" repo is
> -- all the commits should have identical hashes. You could fetch
> commits from one source and then change the source to another, they'd
> still be the same commits. So if you're looking at a particular commit
> hash (or tag) it will be identical in ALL mirrors.
>
> The write-access repository is this:
> https://git-wip-us.apache.org/repos/asf/lucene-solr.git
>
> The read-only view is:
> git://git.apache.org/lucene-solr.git
>
> The same applies to github's mirror (which may be a few commits
> behind, but will still contain identical commits, hashes, etc.)
>
> Dawid
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>


-- 
Anshum Gupta

Re: Apache Lucene/Solr GIT migration, requesting infra help

[Erick Erickson]

Indeed, thanks for your work Dawid and Daniel!!

On Sat, Jan 23, 2016 at 1:34 AM, Michael McCandless
 wrote:
> Thank you Dawid and Daniel for all the hard work here!!
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Sat, Jan 23, 2016 at 4:21 AM, Shalin Shekhar Mangar
>  wrote:
>> Got it, thanks! I'll try your suggestion, Dawid.
>>
>> On Sat, Jan 23, 2016 at 2:36 PM, Dawid Weiss  wrote:
>>> If you're using github then yes, you will need to fork again and
>>> rebase any changes you may have. This can be done by having two
>>> origins locally (two "sources" of commits) -- one from the old clone,
>>> the second one from the new clone. Then you can rebase the branches or
>>> commits you wish and push them to the new clone.
>>>
>>> Dawid
>>>
>>>
>>> On Sat, Jan 23, 2016 at 9:55 AM, Daniel Gruno  wrote:
 On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
> Thanks Dawid and Daniel for all the work!
>
> One strange thing that I noticed is that my fork of apache/lucene-solr
> at https://github.com/shalinmangar/lucene-solr is now shown to be a
> fork of https://github.com/mdodsworth/lucene-solr. I have no idea who
> that guy is. What can we do to fix this?

 Nothing. This is GitHub's fallback method when the original repository
 goes away as it did here (replaced with a new repo with a new history).
 Since referring to the old repo which doesn't exist anymore would break
 your copy, they have fallen back to another copy of it.

 Please re-fork.

 With regards,
 Daniel.

>
> On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss  
> wrote:
>> 1. The content of the lucene-solr.git repository looks good!
>>
>> 2) PROBLEM. I can't push my own branch:
>>
>> $ git co master -b git-check
>> $ [... committed a dummy commit ]
>> $ git push origin HEAD -u
>> fatal: remote error: access denied or repository not exported: 
>> /lucene-solr.git
>>
>> 3) Solr repo is still available for some reason, both as real git repo 
>> here:
>>
>> git://git.apache.org/solr.git
>>
>> and listed here:
>>
>> https://git.apache.org/
>>
>> Could I be seeing a mirror or something?
>>
>> Dawid
>>
>>
>> On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss  
>> wrote:
>>> Checking everything now -- that was fast Daniel!
>>> Dawid
>>>
>>>
>>> On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno  
>>> wrote:
 Just a heads up: Everything is working now and GitHub has caught up 
 with
 the new repository. You should be good to go :)

 With regards,
 Daniel.

 On 01/23/2016 08:36 AM, Daniel Gruno wrote:
> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
>> Hello Daniel,
>>
>> I've prepared everything for the migration and I hand it off to you 
>> (I
>> will be available in the morning, if you need assistance). I can also
>> log on to hipchat, but send me an e-mail if you wish me to.
>>
>> Here are the steps we kindly ask you to perform (I allowed myself to
>> uppercase certain things, apologies if it looks like shouting):
>>
>> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
>> are obsolete and incorrect syncs, consolidated git repo contains full
>> history):
>>
>> git://git.apache.org/solr.git
> DONE
>
>> git://git.apache.org/lucene.git
> DONE
>>
>> 2) Notify (somehow) GitHub that these two repos have been removed
>> (they should not be available or visible on GitHub as well):
>>
>> https://github.com/apache/lucene
> DONE
>> https://github.com/apache/solr
> DONE
>
>>
>> 3) DISABLE svn syncing for the following git mirror:
>>
>> git://git.apache.org/lucene-solr.git
> DONE
>
>>
>> and then REPLACE it (wipe it clean) with the content of the following
>> consolidated repository:
>>
>> g...@github.com:dweiss/lucene-solr-svn2git.git
>>
>> I don't know how it looks from the backend's side, but this should
>> also work, if there are sufficient permissions:
>>
>> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
>> git remote add apache git://git.apache.org/lucene-solr.git
>> git push --mirror apache
> We have our own methods, but nonetheless DONE. Please check that you
> have write-access to the new repo.
>>
>> 4) I don't know if we need to make GitHub aware of the replaced
>> content of the lucene-solr repo 

Re: Apache Lucene/Solr GIT migration, requesting infra help

[Dawid Weiss]

> is the official repo here:
> https://github.com/apache/lucene-solr/tree/releases/lucene-solr/5.4.1
> or
> https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;a=commit;h=f54d853a3c3a2ddcf24ee7e2c837dc4d403bc0b0

With git it does not technically matter which the "official" repo is
-- all the commits should have identical hashes. You could fetch
commits from one source and then change the source to another, they'd
still be the same commits. So if you're looking at a particular commit
hash (or tag) it will be identical in ALL mirrors.

The write-access repository is this:
https://git-wip-us.apache.org/repos/asf/lucene-solr.git

The read-only view is:
git://git.apache.org/lucene-solr.git

The same applies to github's mirror (which may be a few commits
behind, but will still contain identical commits, hashes, etc.)

Dawid

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

RE: Apache Lucene/Solr GIT migration, requesting infra help

[Uwe Schindler]

Thanks Dawid and Daniel,

I am happy with the migration, only one small thing (but its too late to fix 
this):

It is a bit stupid that the last commit in SVN was just reverted and not made 
completely hidden. I would have synced up the converted repo only up to the 
revision before the final *delete all* commit instead of reverting it. Now we 
have a change on every file, which shows 2 useless commits on every file when 
browsing through history. I think we can only remove that 2 commits by 
rewriting history, so not sure. In any case, I am happy.

Uwe

-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de


> -Original Message-
> From: Steve Rowe [mailto:sar...@gmail.com]
> Sent: Saturday, January 23, 2016 10:11 PM
> To: dev@lucene.apache.org
> Cc: Dawid Weiss <dawid.we...@gmail.com>; Daniel Gruno
> <humbed...@apache.org>
> Subject: Re: Apache Lucene/Solr GIT migration, requesting infra help
> 
> Thanks Dawid and Daniel!
> 
> --
> Steve
> www.lucidworks.com
> 
> > On Jan 23, 2016, at 3:45 PM, Erick Erickson <erickerick...@gmail.com>
> wrote:
> >
> > Indeed, thanks for your work Dawid and Daniel!!
> >
> > On Sat, Jan 23, 2016 at 1:34 AM, Michael McCandless
> > <luc...@mikemccandless.com> wrote:
> >> Thank you Dawid and Daniel for all the hard work here!!
> >>
> >> Mike McCandless
> >>
> >> http://blog.mikemccandless.com
> >>
> >>
> >> On Sat, Jan 23, 2016 at 4:21 AM, Shalin Shekhar Mangar
> >> <shalinman...@gmail.com> wrote:
> >>> Got it, thanks! I'll try your suggestion, Dawid.
> >>>
> >>> On Sat, Jan 23, 2016 at 2:36 PM, Dawid Weiss <dawid.we...@gmail.com>
> wrote:
> >>>> If you're using github then yes, you will need to fork again and
> >>>> rebase any changes you may have. This can be done by having two
> >>>> origins locally (two "sources" of commits) -- one from the old clone,
> >>>> the second one from the new clone. Then you can rebase the branches
> or
> >>>> commits you wish and push them to the new clone.
> >>>>
> >>>> Dawid
> >>>>
> >>>>
> >>>> On Sat, Jan 23, 2016 at 9:55 AM, Daniel Gruno
> <humbed...@apache.org> wrote:
> >>>>> On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
> >>>>>> Thanks Dawid and Daniel for all the work!
> >>>>>>
> >>>>>> One strange thing that I noticed is that my fork of apache/lucene-
> solr
> >>>>>> at https://github.com/shalinmangar/lucene-solr is now shown to be
> a
> >>>>>> fork of https://github.com/mdodsworth/lucene-solr. I have no idea
> who
> >>>>>> that guy is. What can we do to fix this?
> >>>>>
> >>>>> Nothing. This is GitHub's fallback method when the original repository
> >>>>> goes away as it did here (replaced with a new repo with a new
> history).
> >>>>> Since referring to the old repo which doesn't exist anymore would
> break
> >>>>> your copy, they have fallen back to another copy of it.
> >>>>>
> >>>>> Please re-fork.
> >>>>>
> >>>>> With regards,
> >>>>> Daniel.
> >>>>>
> >>>>>>
> >>>>>> On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss
> <dawid.we...@gmail.com> wrote:
> >>>>>>> 1. The content of the lucene-solr.git repository looks good!
> >>>>>>>
> >>>>>>> 2) PROBLEM. I can't push my own branch:
> >>>>>>>
> >>>>>>> $ git co master -b git-check
> >>>>>>> $ [... committed a dummy commit ]
> >>>>>>> $ git push origin HEAD -u
> >>>>>>> fatal: remote error: access denied or repository not exported:
> /lucene-solr.git
> >>>>>>>
> >>>>>>> 3) Solr repo is still available for some reason, both as real git repo
> here:
> >>>>>>>
> >>>>>>> git://git.apache.org/solr.git
> >>>>>>>
> >>>>>>> and listed here:
> >>>>>>>
> >>>>>>> https://git.apache.org/
> >>>>>>>
> >>>>>>> Could I be seeing a mirror or something?
> >>>>>>>
> >>

Re: Apache Lucene/Solr GIT migration, requesting infra help

[Daniel Gruno]

On 01/23/2016 03:02 AM, Dawid Weiss wrote:
> Hello Daniel,
> 
> I've prepared everything for the migration and I hand it off to you (I
> will be available in the morning, if you need assistance). I can also
> log on to hipchat, but send me an e-mail if you wish me to.
> 
> Here are the steps we kindly ask you to perform (I allowed myself to
> uppercase certain things, apologies if it looks like shouting):
> 
> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
> are obsolete and incorrect syncs, consolidated git repo contains full
> history):
> 
> git://git.apache.org/solr.git
DONE

> git://git.apache.org/lucene.git
DONE
> 
> 2) Notify (somehow) GitHub that these two repos have been removed
> (they should not be available or visible on GitHub as well):
> 
> https://github.com/apache/lucene
DONE
> https://github.com/apache/solr
DONE

> 
> 3) DISABLE svn syncing for the following git mirror:
> 
> git://git.apache.org/lucene-solr.git
DONE

> 
> and then REPLACE it (wipe it clean) with the content of the following
> consolidated repository:
> 
> g...@github.com:dweiss/lucene-solr-svn2git.git
> 
> I don't know how it looks from the backend's side, but this should
> also work, if there are sufficient permissions:
> 
> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
> git remote add apache git://git.apache.org/lucene-solr.git
> git push --mirror apache
We have our own methods, but nonetheless DONE. Please check that you
have write-access to the new repo.
> 
> 4) I don't know if we need to make GitHub aware of the replaced
> content of the lucene-solr repo or if their syncing will handle this
> automatically. It would be nice if they could catch up as quickly as
> possible.

As explained on the JIRA ticket, if we're lucky, this should happen
automagically in about 20 minutes from now. If not, we'll have to wait
24 hours. Time will tell :)

With regards,
Daniel.

> 
> In case of questions, problems or a successful import, please drop me
> an e-mail. Oh, thank you for being so nice and helping us on your day
> off -- much appreciated.
> 
> Dawid
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Apache Lucene/Solr GIT migration, requesting infra help

[Dawid Weiss]

Hello Daniel,

I've prepared everything for the migration and I hand it off to you (I
will be available in the morning, if you need assistance). I can also
log on to hipchat, but send me an e-mail if you wish me to.

Here are the steps we kindly ask you to perform (I allowed myself to
uppercase certain things, apologies if it looks like shouting):

1) Permanently REMOVE the following git mirrors of SVN (reason: they
are obsolete and incorrect syncs, consolidated git repo contains full
history):

git://git.apache.org/solr.git
git://git.apache.org/lucene.git

2) Notify (somehow) GitHub that these two repos have been removed
(they should not be available or visible on GitHub as well):

https://github.com/apache/lucene
https://github.com/apache/solr

3) DISABLE svn syncing for the following git mirror:

git://git.apache.org/lucene-solr.git

and then REPLACE it (wipe it clean) with the content of the following
consolidated repository:

g...@github.com:dweiss/lucene-solr-svn2git.git

I don't know how it looks from the backend's side, but this should
also work, if there are sufficient permissions:

git clone g...@github.com:dweiss/lucene-solr-svn2git.git
git remote add apache git://git.apache.org/lucene-solr.git
git push --mirror apache

4) I don't know if we need to make GitHub aware of the replaced
content of the lucene-solr repo or if their syncing will handle this
automatically. It would be nice if they could catch up as quickly as
possible.

In case of questions, problems or a successful import, please drop me
an e-mail. Oh, thank you for being so nice and helping us on your day
off -- much appreciated.

Dawid

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org