diff options
Diffstat (limited to 'doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__')
2 files changed, 0 insertions, 39 deletions
diff --git a/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_1_0ddcbe0ccecdec1012964dfa436a3eee._comment b/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_1_0ddcbe0ccecdec1012964dfa436a3eee._comment deleted file mode 100644 index ef2399d81..000000000 --- a/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_1_0ddcbe0ccecdec1012964dfa436a3eee._comment +++ /dev/null @@ -1,19 +0,0 @@ -[[!comment format=mdwn - username="http://joeyh.name/" - ip="64.134.31.139" - subject="comment 1" - date="2013-10-23T15:21:34Z" - content=""" -<pre> -To ssh://schmitta@git-annex-**.**.**.**-schmitta_annex.2Farchive/~/annex/archive/ - ! [remote rejected] git-annex -> synced/git-annex (non-fast-forward) -</pre> - -Since version 4.20130909, git-annex is supposed to have avoided this problem by forcing the push of the git-annex branch. If you run `git annex sync --debug`, you should see: - -[2013-10-23 11:12:54 EDT] call: git [\"--git-dir=annex/.git\",\"--work-tree=annex\",\"push\",\"foo\",\"+git-annex:synced/git-annex\",\"master:synced/master\"] - -The \"+\" flag before the branch name forces git push to update the remote branch even if it's not a fast-forward. - -You should be able to verify if git-annex is doing that, and run the same git push command manually to investigate why it might not be working. I have not seen this problem since putting in that fix, and I saw it before. Perhaps your server has an old or broken version of git that ignores this flag, or some git configuration setting I am not aware of that prevents it from working. -"""]] diff --git a/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_2_5765b849bcf045ead9f007bd50b2cfbd._comment b/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_2_5765b849bcf045ead9f007bd50b2cfbd._comment deleted file mode 100644 index 44ccfe00b..000000000 --- a/doc/bugs/How_can_I_solve_a_non-fast-forward_push_without_using_the_assistant__63__/comment_2_5765b849bcf045ead9f007bd50b2cfbd._comment +++ /dev/null @@ -1,20 +0,0 @@ -[[!comment format=mdwn - username="http://alan.petitepomme.net/" - nickname="Alan Schmitt" - subject="comment 2" - date="2013-10-23T16:21:30Z" - content=""" -I think I found the problem, after much googling. - -The command line you suggest is indeed tried, and rejected by the server. - -The answer came from [here](http://stackoverflow.com/questions/253055/how-do-i-push-amended-commit-to-the-remote-git-repo) where it says (speaking of a forced push) - -> Even this may not work as git allows remote repositories to refuse non-fastforward pushes at the far end by using the config variable 'receive.denynonfastforwards'. - -Indeed this is set in my annex repository. Note that this is a local setting, and that repository was created by the assistant. - -I removed this setting, and I can now push. Could the setting of this bit be a bug in the assistant? - -In any case, thanks a lot for indicating where to look at. -"""]] |