Google + Mercurial is seriously broken!

Martin Hodge Posts: 1,246

2012-07-10 07:15 edited 2012-07-21 06:03 in Propeller 1

This has been a problem from the beginning of this project, but over the past two days the problem has become chronic.

martin@martin-Inspiron-620:~$ cd prop
martin@martin-Inspiron-620:~/prop$ hg clone https://code.google.com/p/propgcc/
destination directory: propgcc
requesting all changes
adding changesets
adding manifests
transaction abort!
rollback completed
abort: connection ended unexpectedly
martin@martin-Inspiron-620:~/prop$ hg clone http://code.google.com/p/propgcc/
destination directory: propgcc
requesting all changes
adding changesets
adding manifests
transaction abort!
rollback completed
abort: connection ended unexpectedly
martin@martin-Inspiron-620:~/prop$

Comments

jazzed Posts: 11,803

2012-07-10 07:28 edited 2012-07-10 07:28

Martin, just keep trying.

I've had to try up to 5 times. I feel the pain.
The number of files is probably responsible for most of the trouble.
I'll try cloning it and changing to git to see if it works any better.

Martin Hodge wrote: »

This has been a problem from the beginning of this project, but over the past two days the problem has become chronic.
Heater. Posts: 21,230

2012-07-10 07:31 edited 2012-07-10 07:31

Yep, I have seen that happening a lot too.
Martin Hodge Posts: 1,246

2012-07-10 07:40 edited 2012-07-10 07:40

jazzed wrote: »

I've had to try up to 5 times.

I gave up at around 20 to 30 tries in rapid succcession.
pedward Posts: 1,642

2012-07-10 12:25 edited 2012-07-10 12:25

I feel HG adds unnecessary complexity. I really like how straightforward SVN is. The only caveat is merges, but HG seems to really get that wrong too. SVN is very simple and straightforward when you merge, it does so automatically or generates conflict files you can edit manually and mark "resolved".

I use SVN in a multi-developer environment and the rule of thumb is "update to head" regularly. Eclipse manages SVN integration very well, eliminating much of the oddball nature.

The big difference between SVN and HG&GIT is that you needn't clone the entire history of civilisation to get the latest rev. It's a thin client model, whereas HG&GIT aren't, and that compounds the problem you are experiencing.

The PropGCC repo is several GB in size, and needlessly so.
Kye Posts: 2,200

2012-07-10 12:46 edited 2012-07-10 12:46

Hmm, with SVN you lose the ability for private version control on your own repo. But, I do like the simplicity.

It HG is failing though. Then there's reason to swtich.

Thanks,
pedward Posts: 1,642

2012-07-10 14:14 edited 2012-07-10 14:14

You can get around the private repos by branching and merging the trunk into your branch.

I do find branching to be problematic and prefer working from the trunk, to force the responsibility of merging onto the submitter, rather than consumer.

I feel it is the submitter's responsibility to ensure their changes don't break the build, and forcing them to merge on checkin is one way to prevent that.

Otherwise, if someone checks in a conflicting change, I'm forced to integrate their work and I may break their code as a result.

My first experience with checkin on HG resulted in needless hoops WRT merges. I could see the solution plain as day, but it made the process so frustrating.
yeti Posts: 819

2012-07-21 06:03 edited 2012-07-21 06:03

Using --debug when cloning the repo seems to change more in hg's behaviour than just giving more output.
Maybe it influences some timeouts too?
When giving --debug cloning fails far less often.
Without --debug I never was able to clone propgcc.
Updating the repo (the local clone) without --debug always was no problem here.

or Register to comment.