You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Dawid Weiss (JIRA)" <ji...@apache.org> on 2011/06/16 08:52:47 UTC
[jira] [Created] (INFRA-3689) rsync access to git mirrors of svn
repositories
rsync access to git mirrors of svn repositories
-----------------------------------------------
Key: INFRA-3689
URL: https://issues.apache.org/jira/browse/INFRA-3689
Project: Infrastructure
Issue Type: New Feature
Security Level: public (Regular issues)
Components: Git, Subversion
Reporter: Dawid Weiss
git-svn stores metadata in an svn mirror that is hard to reproduce after you do a clone from such a repository. This means that while you can do git pulls, you can't do git svn dcommit, which would be such a nice feature to have. I've tried to do it several times and failed and I know of a few other people that couldn't do it either.
A simple solution to this problem would be to expose git repositories using rsync; this would allow folks to mirror the full repository, including svn metadata, and then rebase/ dcommit to their liking.
I did a proof of concept of this by fetching a mirror of apache lucene reopsitory using wget -m -np, then manually (find -exec rm...) pruning index.html files and converting bare=true to bare=false. Works like a charm.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (INFRA-3689) rsync access to git
mirrors of svn repositories
Posted by "Dawid Weiss (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050279#comment-13050279 ]
Dawid Weiss edited comment on INFRA-3689 at 6/16/11 8:14 AM:
-------------------------------------------------------------
To be exact, the log:
git clone git://git.apache.org/lucene-solr.git
cd lucene-solr
# wget authors file, config svn.authorsfile, etc., then
# note lucene's svn has been reorganized in the past; the current layout is under java folder, but is standard (-s)
git svn init --prefix=origin/ -s https://svn.apache.org/repos/asf/lucene/java
git svn rebase
Unable to determine upstream SVN information from working tree history
rsync would have worked for me, but sure - I can mirror (once) over http... I just thought it'd be easier to provide rsync access since there is a http one already.
was (Author: dweiss):
To be exact, the log:
{noformat}
git clone git://git.apache.org/lucene-solr.git
cd lucene-solr
# wget authors file, config svn.authorsfile, etc., then
# note lucene's svn has been reorganized in the past; the current layout is under java folder, but is standard (-s)
git svn init --prefix=origin/ -s https://svn.apache.org/repos/asf/lucene/java
git svn rebase
Unable to determine upstream SVN information from working tree history
{noformat}
rsync would have worked for me, but I can mirror (once) over http... I just thought it'd be easier to provide rsync access since there is a http one already.
> rsync access to git mirrors of svn repositories
> -----------------------------------------------
>
> Key: INFRA-3689
> URL: https://issues.apache.org/jira/browse/INFRA-3689
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Git, Subversion
> Reporter: Dawid Weiss
>
> git-svn stores metadata in an svn mirror that is hard to reproduce after you do a clone from such a repository. This means that while you can do git pulls, you can't do git svn dcommit, which would be such a nice feature to have. I've tried to do it several times and failed and I know of a few other people that couldn't do it either.
> A simple solution to this problem would be to expose git repositories using rsync; this would allow folks to mirror the full repository, including svn metadata, and then rebase/ dcommit to their liking.
> I did a proof of concept of this by fetching a mirror of apache lucene reopsitory using wget -m -np, then manually (find -exec rm...) pruning index.html files and converting bare=true to bare=false. Works like a charm.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3689) rsync access to git mirrors of svn
repositories
Posted by "Dawid Weiss (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050279#comment-13050279 ]
Dawid Weiss commented on INFRA-3689:
------------------------------------
To be exact, the log:
{noformat}
git clone git://git.apache.org/lucene-solr.git
cd lucene-solr
# wget authors file, config svn.authorsfile, etc., then
# note lucene's svn has been reorganized in the past; the current layout is under java folder, but is standard (-s)
git svn init --prefix=origin/ -s https://svn.apache.org/repos/asf/lucene/java
git svn rebase
Unable to determine upstream SVN information from working tree history
{noformat}
rsync would have worked for me, but I can mirror (once) over http... I just thought it'd be easier to provide rsync access since there is a http one already.
> rsync access to git mirrors of svn repositories
> -----------------------------------------------
>
> Key: INFRA-3689
> URL: https://issues.apache.org/jira/browse/INFRA-3689
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Git, Subversion
> Reporter: Dawid Weiss
>
> git-svn stores metadata in an svn mirror that is hard to reproduce after you do a clone from such a repository. This means that while you can do git pulls, you can't do git svn dcommit, which would be such a nice feature to have. I've tried to do it several times and failed and I know of a few other people that couldn't do it either.
> A simple solution to this problem would be to expose git repositories using rsync; this would allow folks to mirror the full repository, including svn metadata, and then rebase/ dcommit to their liking.
> I did a proof of concept of this by fetching a mirror of apache lucene reopsitory using wget -m -np, then manually (find -exec rm...) pruning index.html files and converting bare=true to bare=false. Works like a charm.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3689) rsync access to git mirrors of svn
repositories
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050275#comment-13050275 ]
Gavin commented on INFRA-3689:
------------------------------
Please join the infrastructure-dev@ list and ask there. There are literally hundreds of people using it quite successfully. We wont be exposing it to rsync, thanks.
> rsync access to git mirrors of svn repositories
> -----------------------------------------------
>
> Key: INFRA-3689
> URL: https://issues.apache.org/jira/browse/INFRA-3689
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Git, Subversion
> Reporter: Dawid Weiss
>
> git-svn stores metadata in an svn mirror that is hard to reproduce after you do a clone from such a repository. This means that while you can do git pulls, you can't do git svn dcommit, which would be such a nice feature to have. I've tried to do it several times and failed and I know of a few other people that couldn't do it either.
> A simple solution to this problem would be to expose git repositories using rsync; this would allow folks to mirror the full repository, including svn metadata, and then rebase/ dcommit to their liking.
> I did a proof of concept of this by fetching a mirror of apache lucene reopsitory using wget -m -np, then manually (find -exec rm...) pruning index.html files and converting bare=true to bare=false. Works like a charm.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3689) rsync access to git mirrors of svn
repositories
Posted by "Dawid Weiss (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050286#comment-13050286 ]
Dawid Weiss commented on INFRA-3689:
------------------------------------
Ok, thanks Tony. I know about rebase problems and the mirror also screws up dcommits (rebase is done as part of that). No problem with these though -- can be lived with. The problem is (I think) stemming from lucene's codebase being shuffled around the repository -- I can't reproduce git svn metadata from a git clone. Things work just fine if I fetch them from the mirror directly (wget).
> rsync access to git mirrors of svn repositories
> -----------------------------------------------
>
> Key: INFRA-3689
> URL: https://issues.apache.org/jira/browse/INFRA-3689
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Git, Subversion
> Reporter: Dawid Weiss
>
> git-svn stores metadata in an svn mirror that is hard to reproduce after you do a clone from such a repository. This means that while you can do git pulls, you can't do git svn dcommit, which would be such a nice feature to have. I've tried to do it several times and failed and I know of a few other people that couldn't do it either.
> A simple solution to this problem would be to expose git repositories using rsync; this would allow folks to mirror the full repository, including svn metadata, and then rebase/ dcommit to their liking.
> I did a proof of concept of this by fetching a mirror of apache lucene reopsitory using wget -m -np, then manually (find -exec rm...) pruning index.html files and converting bare=true to bare=false. Works like a charm.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3689) rsync access to git mirrors of svn
repositories
Posted by "Dawid Weiss (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050291#comment-13050291 ]
Dawid Weiss commented on INFRA-3689:
------------------------------------
I compared .config files on both repos -- I used
https://svn.apache.org/repos/asf/lucene/java/trunk
and it should have been
https://svn.apache.org/repos/asf/lucene/dev/trunk
After that, svn rebase seems to work fine. I'll double check just to make sure, but thanks for help and apologies for this false alarm.
> rsync access to git mirrors of svn repositories
> -----------------------------------------------
>
> Key: INFRA-3689
> URL: https://issues.apache.org/jira/browse/INFRA-3689
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Git, Subversion
> Reporter: Dawid Weiss
>
> git-svn stores metadata in an svn mirror that is hard to reproduce after you do a clone from such a repository. This means that while you can do git pulls, you can't do git svn dcommit, which would be such a nice feature to have. I've tried to do it several times and failed and I know of a few other people that couldn't do it either.
> A simple solution to this problem would be to expose git repositories using rsync; this would allow folks to mirror the full repository, including svn metadata, and then rebase/ dcommit to their liking.
> I did a proof of concept of this by fetching a mirror of apache lucene reopsitory using wget -m -np, then manually (find -exec rm...) pruning index.html files and converting bare=true to bare=false. Works like a charm.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3689) rsync access to git mirrors of svn
repositories
Posted by "Tony Stevenson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050283#comment-13050283 ]
Tony Stevenson commented on INFRA-3689:
---------------------------------------
We do not provide rsync access to the repositories. Sorry.
Did you see the comment in the wiki pages about rebasing when in EU?
> rsync access to git mirrors of svn repositories
> -----------------------------------------------
>
> Key: INFRA-3689
> URL: https://issues.apache.org/jira/browse/INFRA-3689
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Git, Subversion
> Reporter: Dawid Weiss
>
> git-svn stores metadata in an svn mirror that is hard to reproduce after you do a clone from such a repository. This means that while you can do git pulls, you can't do git svn dcommit, which would be such a nice feature to have. I've tried to do it several times and failed and I know of a few other people that couldn't do it either.
> A simple solution to this problem would be to expose git repositories using rsync; this would allow folks to mirror the full repository, including svn metadata, and then rebase/ dcommit to their liking.
> I did a proof of concept of this by fetching a mirror of apache lucene reopsitory using wget -m -np, then manually (find -exec rm...) pruning index.html files and converting bare=true to bare=false. Works like a charm.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (INFRA-3689) rsync access to git mirrors of svn
repositories
Posted by "Tony Stevenson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tony Stevenson closed INFRA-3689.
---------------------------------
Thanks for clearing up.
> rsync access to git mirrors of svn repositories
> -----------------------------------------------
>
> Key: INFRA-3689
> URL: https://issues.apache.org/jira/browse/INFRA-3689
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Git, Subversion
> Reporter: Dawid Weiss
>
> git-svn stores metadata in an svn mirror that is hard to reproduce after you do a clone from such a repository. This means that while you can do git pulls, you can't do git svn dcommit, which would be such a nice feature to have. I've tried to do it several times and failed and I know of a few other people that couldn't do it either.
> A simple solution to this problem would be to expose git repositories using rsync; this would allow folks to mirror the full repository, including svn metadata, and then rebase/ dcommit to their liking.
> I did a proof of concept of this by fetching a mirror of apache lucene reopsitory using wget -m -np, then manually (find -exec rm...) pruning index.html files and converting bare=true to bare=false. Works like a charm.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (INFRA-3689) rsync access to git mirrors of svn
repositories
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
#asfinfra IRC Bot closed INFRA-3689.
------------------------------------
Resolution: Fixed
> rsync access to git mirrors of svn repositories
> -----------------------------------------------
>
> Key: INFRA-3689
> URL: https://issues.apache.org/jira/browse/INFRA-3689
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Git, Subversion
> Reporter: Dawid Weiss
>
> git-svn stores metadata in an svn mirror that is hard to reproduce after you do a clone from such a repository. This means that while you can do git pulls, you can't do git svn dcommit, which would be such a nice feature to have. I've tried to do it several times and failed and I know of a few other people that couldn't do it either.
> A simple solution to this problem would be to expose git repositories using rsync; this would allow folks to mirror the full repository, including svn metadata, and then rebase/ dcommit to their liking.
> I did a proof of concept of this by fetching a mirror of apache lucene reopsitory using wget -m -np, then manually (find -exec rm...) pruning index.html files and converting bare=true to bare=false. Works like a charm.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (INFRA-3689) rsync access to git mirrors of svn
repositories
Posted by "Dawid Weiss (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dawid Weiss resolved INFRA-3689.
--------------------------------
Resolution: Not A Problem
Ok, I'll ask around.
> rsync access to git mirrors of svn repositories
> -----------------------------------------------
>
> Key: INFRA-3689
> URL: https://issues.apache.org/jira/browse/INFRA-3689
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Git, Subversion
> Reporter: Dawid Weiss
>
> git-svn stores metadata in an svn mirror that is hard to reproduce after you do a clone from such a repository. This means that while you can do git pulls, you can't do git svn dcommit, which would be such a nice feature to have. I've tried to do it several times and failed and I know of a few other people that couldn't do it either.
> A simple solution to this problem would be to expose git repositories using rsync; this would allow folks to mirror the full repository, including svn metadata, and then rebase/ dcommit to their liking.
> I did a proof of concept of this by fetching a mirror of apache lucene reopsitory using wget -m -np, then manually (find -exec rm...) pruning index.html files and converting bare=true to bare=false. Works like a charm.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3689) rsync access to git mirrors of svn
repositories
Posted by "Tony Stevenson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050276#comment-13050276 ]
Tony Stevenson commented on INFRA-3689:
---------------------------------------
Hey,
Why not paste something so we can see what you see, rather than just guessing. Perhaps also describe your environment and what commands you are running etc.
Help us help you.
> rsync access to git mirrors of svn repositories
> -----------------------------------------------
>
> Key: INFRA-3689
> URL: https://issues.apache.org/jira/browse/INFRA-3689
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Git, Subversion
> Reporter: Dawid Weiss
>
> git-svn stores metadata in an svn mirror that is hard to reproduce after you do a clone from such a repository. This means that while you can do git pulls, you can't do git svn dcommit, which would be such a nice feature to have. I've tried to do it several times and failed and I know of a few other people that couldn't do it either.
> A simple solution to this problem would be to expose git repositories using rsync; this would allow folks to mirror the full repository, including svn metadata, and then rebase/ dcommit to their liking.
> I did a proof of concept of this by fetching a mirror of apache lucene reopsitory using wget -m -np, then manually (find -exec rm...) pruning index.html files and converting bare=true to bare=false. Works like a charm.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3689) rsync access to git mirrors of svn
repositories
Posted by "Dawid Weiss (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050271#comment-13050271 ]
Dawid Weiss commented on INFRA-3689:
------------------------------------
Like I said, I've tried that. Unfortunately, this doesn't work -- bails out with an error on Apache Lucene (Java) saying couldn't find the proper history or something.
> rsync access to git mirrors of svn repositories
> -----------------------------------------------
>
> Key: INFRA-3689
> URL: https://issues.apache.org/jira/browse/INFRA-3689
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Git, Subversion
> Reporter: Dawid Weiss
>
> git-svn stores metadata in an svn mirror that is hard to reproduce after you do a clone from such a repository. This means that while you can do git pulls, you can't do git svn dcommit, which would be such a nice feature to have. I've tried to do it several times and failed and I know of a few other people that couldn't do it either.
> A simple solution to this problem would be to expose git repositories using rsync; this would allow folks to mirror the full repository, including svn metadata, and then rebase/ dcommit to their liking.
> I did a proof of concept of this by fetching a mirror of apache lucene reopsitory using wget -m -np, then manually (find -exec rm...) pruning index.html files and converting bare=true to bare=false. Works like a charm.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3689) rsync access to git mirrors of svn
repositories
Posted by "Paul Querna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050242#comment-13050242 ]
Paul Querna commented on INFRA-3689:
------------------------------------
You don't need rsync to do this.
See the section "Git for Apache committers":
http://wiki.apache.org/general/GitAtApache
> rsync access to git mirrors of svn repositories
> -----------------------------------------------
>
> Key: INFRA-3689
> URL: https://issues.apache.org/jira/browse/INFRA-3689
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Git, Subversion
> Reporter: Dawid Weiss
>
> git-svn stores metadata in an svn mirror that is hard to reproduce after you do a clone from such a repository. This means that while you can do git pulls, you can't do git svn dcommit, which would be such a nice feature to have. I've tried to do it several times and failed and I know of a few other people that couldn't do it either.
> A simple solution to this problem would be to expose git repositories using rsync; this would allow folks to mirror the full repository, including svn metadata, and then rebase/ dcommit to their liking.
> I did a proof of concept of this by fetching a mirror of apache lucene reopsitory using wget -m -np, then manually (find -exec rm...) pruning index.html files and converting bare=true to bare=false. Works like a charm.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (INFRA-3689) rsync access to git mirrors of svn
repositories
Posted by "Dawid Weiss (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dawid Weiss reopened INFRA-3689:
--------------------------------
> rsync access to git mirrors of svn repositories
> -----------------------------------------------
>
> Key: INFRA-3689
> URL: https://issues.apache.org/jira/browse/INFRA-3689
> Project: Infrastructure
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: Git, Subversion
> Reporter: Dawid Weiss
>
> git-svn stores metadata in an svn mirror that is hard to reproduce after you do a clone from such a repository. This means that while you can do git pulls, you can't do git svn dcommit, which would be such a nice feature to have. I've tried to do it several times and failed and I know of a few other people that couldn't do it either.
> A simple solution to this problem would be to expose git repositories using rsync; this would allow folks to mirror the full repository, including svn metadata, and then rebase/ dcommit to their liking.
> I did a proof of concept of this by fetching a mirror of apache lucene reopsitory using wget -m -np, then manually (find -exec rm...) pruning index.html files and converting bare=true to bare=false. Works like a charm.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira