Hello Michael,
On Thu, 02 Jun 2011 21:18:44 +1200 Michael Hudson-Doyle michael.hudson@linaro.org wrote:
[]
Once I moved that ".git.git" repo away, original issue with repo sync resolved. I have no idea that double-.git repo was created. Based on the timestamp, it was created first, and later barely updated, with mirror and just git clone using the proper repo, while repo sync on the build slave managing to pick up wrong one. I wonder, if that (creation of 2 repos) could be a result of some race condition.
I bet it is.
And it's not the only case, but at least not regular:
ubuntu@android-build:/mnt/mirror$ find -type d -name '*.git.git' ./git.omapzoom.org/kernel/omap.git.git
What's interesting is that this is again a kernel repository. I'm not sure what to do about it now, considering just to set up a cronjob which will use that find command (need to figure out how to send mail from ec2).
And I wish this issue could be called resolved, but as quoted above, there're (more) issues are known with git --mirror, so I decided to put up this mail with the links, for the next time such issues may come.
As you pointed out to me fairly soon after you started, we don't actually need to run "repo sync" on the server at all -- it's not hard to figure out the "git clone" commands we need to run, and so maybe we (well, you :-p) should just do that.
Yes, I still keep that in mind, wanted to try it for this case, when it suddenly resolved. All in all, current mirror system seems to work (even though sometimes workarounds are required), while some stuff still missing, so I guess this will need to wait a bit...
Cheers, mwh