Closed Bug 815493 Opened 12 years ago Closed 12 years ago

can't clone hg.m.o:integration/gaia over http

Categories

(Developer Services :: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: hwine, Assigned: bkero)

References

Details

(Whiteboard: [reit-b2g])

Even using the build-vpn servers. Nick got: 20:02 <@nthomas> [cltbld@bld-centos6-hp-001 foo]$ hg clone http://hg-internal.dmz.scl3.mozilla.com/integration/gaia 20:02 <@nthomas> destination directory: gaia 20:02 <@nthomas> requesting all changes 20:02 <@nthomas> abort: HTTP Error 413: Request Entity Too Large This is key to using the repo within the build-vpn, and meeting Dec 10 dates. What options do we have here?
An idea from :nthomas - if you enable bundles, our tooling will handle that properly. Is that easy for you?
This is a bit strange given there are about 20k changesets in repo, while mozilla-central is over 110K. Are there different apache configs for some repos ?
Assignee: server-ops-devservices → bkero
(In reply to Nick Thomas [:nthomas] from comment #2) > This is a bit strange given there are about 20k changesets in repo, while > mozilla-central is over 110K. Are there different apache configs for some > repos ? Not that I know of, no.
what hg version is the client using? sounds like it is < 1.8
Seems to fail on a number of version - definitely on hg 2.0 There are a huge number of heads in this repo, so may be similar to the try issues we had previously. There are 3,917 heads.
Assignee: bkero → hwine
I have a fix*, but it requires that the hg repo at hg.mozilla.org/integration/gaia be reset to empty. Please reset the repo and page me when completed. * the fix is to only pull & push the branches of interest, never bringing over the other heads. Since this is not the RoR, that is a reasonable approach.
Assignee: hwine → server-ops-devservices
repo reset
Assignee: server-ops-devservices → bkero
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Component: Server Operations: Developer Services → General
Product: mozilla.org → Developer Services
You need to log in before you can comment on or make changes to this bug.