Community
Participate
Working Groups
running from orion.eclipse.org 0.2.0.v20110915-1812 yesterday I cloned the org.eclipse.orion.client database, grabbing the link from the planet orion news. I did some work, committed to local, and am now failing when I try to push change, with error 500 while running opperation: remote does not support smart HTTP push This confused me at first, but I'm wondering if I caused this by using an http link (the one from planet orion?) http://git.eclipse.org/c/orion/org.eclipse.orion.client.git At this point, what can I do to push my change? - change a property on the repository? Minor nit: the word "operation" is misspelled in the error message (two p's). marking major, since I can't push. If you can help me with a workflow to either fix the repo or reclone and set my local to point to the remote, that would be fine for now.
John helped me get going here. I changed the repository URL on the clones page to use ssh. So maybe the to-do for this bug is: - fix the spelling error - maybe warn the user if they are cloning using a read only protocol? I probably would have caught my error at that point... decreasing severity.
The typo has been fixed with http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=5e54492dc54c2f06d0ca3462cd5132e03a0fadb0. As for the warning, I have a doubt. AFAIK it’s possible to push over HTTP, but it's a rare configuration indeed.
(In reply to comment #2) > The typo has been fixed with > http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=5e54492dc54c2f06d0ca3462cd5132e03a0fadb0. > > As for the warning, I have a doubt. AFAIK it’s possible to push over HTTP, but > it's a rare configuration indeed. The good news is that the error message was specific, so as soon as I realized what URL I had used, I knew why it was happening. So maybe the error message just needs to make a suggestion? Something like: error 500 while running operation: Remote does not support smart HTTP push. You will need to use an alternate protocol, such as ssh, to push changes.
(In reply to comment #3) > The good news is that the error message was specific, so as soon as I realized > what URL I had used, I knew why it was happening. So maybe the error message > just needs to make a suggestion? Or maybe we should just show a link to a page with hints?
I've hit this several times. I think you need a solution. BTW: The googlecode git system does not use git:// at all, only HTTPS. http://code.google.com/p/support/wiki/GitFAQ Let me know I can ask them if they have a suggestion for this issue. Maybe two links to clone? Clone Writable Repository Clone Readable Repository Then do some test to verify?
(In reply to comment #4) > (In reply to comment #3) > > The good news is that the error message was specific, so as soon as I realized > > what URL I had used, I knew why it was happening. So maybe the error message > > just needs to make a suggestion? > > Or maybe we should just show a link to a page with hints? opened bug 359271
*** Bug 354751 has been marked as a duplicate of this bug. ***
(In reply to Susan McCourt from comment #0) > running from orion.eclipse.org > 0.2.0.v20110915-1812 > > yesterday I cloned the org.eclipse.orion.client database, grabbing the link > from the planet orion news. I did some work, committed to local, and am now > failing when I try to push change, with > > error 500 while running opperation: remote does not support smart HTTP push > > This confused me at first, but I'm wondering if I caused this by using an > http link (the one from planet orion?) > http://git.eclipse.org/c/orion/org.eclipse.orion.client.git > > At this point, what can I do to push my change? > - change a property on the repository? http://git.eclipse.org/c/orion/org.eclipse.orion.client.git is served by cgit (http://git.zx2c4.com/cgit/about/) which is mainly used to browse git repositories online using a browser, it only implements git's dumb HTTP protocol which shouldn't be used for git commands as it is dumb and very slow.
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html
