mercurial hg - pushing to a cloned repositor via APACHE errors with "repository is unrelated"
- by Ash
Two scenarios, one work one doesn't when they both should:
Scenario #1: (DOES NOT work via apache)
2 repos on Server SERVER: Repo "A", Repo "B" cloned from repo A via http://SERVER/HG/A
On client:
Repo A cloned from http://SERVER/HG/A
Repo B cloned from http://SERVER/HG/B
Added a file to repo A from client and commited & pushed it up to http://SERVER/HG/A ...WORKS
Added a file to repo B from client and commited & pushed it up to http://SERVER/HG/B ...ERROR with abort: repository is unrelated, it only works if I -f (force) the push
Scenario #2: (works via file system)
On Server SERVER: Repo "A", Repo "B" cloned from E:/HG/A
On client:
Repo A cloned from E:/HG/A
Repo B cloned from E:/HG/B
Added a file to repo A from client and commited & pushed it up to E:/HG/A ...WORKS
Added a file to repo B from client and commited & pushed it up to E:/HG/B ...WORKS
Conclusion:...Something in the apache configuration or in the integration between apache & mercurial is making the repo "unrelated"....
Any ideas??? Why do I need to force in the first scenario but do not have to in the second??
...and i tried both scenarios via tortoisehg as well as command line.
