Hg problem?

Hg problem?

[Nakajima, Jun]

I keep getting the following errors on different machines (x86_32 and
x86_64). Hg version is 0.6c.

searching for changes
adding changesets
adding manifests
adding file changes
Traceback (most recent call last):
  File "/usr/bin/hg", line 13, in ?
    commands.run()
  File "/usr/lib64/python2.3/site-packages/mercurial/commands.py", line
1461, in run
    sys.exit(dispatch(sys.argv[1:]))
  File "/usr/lib64/python2.3/site-packages/mercurial/commands.py", line
1571, in dispatch
    return d()
  File "/usr/lib64/python2.3/site-packages/mercurial/commands.py", line
1556, in <lambda>
    d = lambda: func(u, repo, *args, **cmdoptions)
  File "/usr/lib64/python2.3/site-packages/mercurial/commands.py", line
938, in pull
    r = repo.pull(other)
  File "/usr/lib64/python2.3/site-packages/mercurial/hg.py", line 1404,
in pull
    return self.addchangegroup(cg)
  File "/usr/lib64/python2.3/site-packages/mercurial/hg.py", line 1526,
in addchangegroup
    n = fl.addgroup(getgroup(), revmap, tr)
  File "/usr/lib64/python2.3/site-packages/mercurial/revlog.py", line
517, in addgroup
    raise "unknown base %s" % short(chain[:4])
unknown base 4ff10995
transaction abort!
rollback completed

Jun
---
Intel Open Source Technology Center 

Re: Hg problem?

[Chris Bainbridge]

On 08/09/05, Nakajima, Jun <jun.nakajima@intel.com> wrote:
> I keep getting the following errors on different machines (x86_32 and
> x86_64). Hg version is 0.6c.

Were you trying to use a seed archive? I kept getting errors using the
unstable seed tarballs. A 'hg pull' of the whole repository worked
fine.

RE: Hg problem?

[Nakajima, Jun]

Chris Bainbridge wrote:
> On 08/09/05, Nakajima, Jun <jun.nakajima@intel.com> wrote:
>> I keep getting the following errors on different machines (x86_32 and
>> x86_64). Hg version is 0.6c.
> 
> Were you trying to use a seed archive? I kept getting errors using the
> unstable seed tarballs. A 'hg pull' of the whole repository worked
> fine.
> 
Actually I tried two things, a seed archive and the local tree I was
using, which used to be working until today. Anyway, it worked fine if I
pull the whole repository. 

Thanks.

Jun
---
Intel Open Source Technology Center

RE: Hg problem?

[Ian Pratt]

> On 08/09/05, Nakajima, Jun <jun.nakajima@intel.com> wrote:
> > I keep getting the following errors on different machines 
> (x86_32 and 
> > x86_64). Hg version is 0.6c.
> 
> Were you trying to use a seed archive? I kept getting errors 
> using the unstable seed tarballs. A 'hg pull' of the whole 
> repository worked fine.

Yes, the seed repositories only work with 0.6b due to the directory name
'init.d' issue. We either need to update them or delete them.

Ian

RE: Hg problem?

[Nakajima, Jun]

Ian Pratt wrote:
>> On 08/09/05, Nakajima, Jun <jun.nakajima@intel.com> wrote:
>>> I keep getting the following errors on different machines (x86_32
>>> and x86_64). Hg version is 0.6c.
>> 
>> Were you trying to use a seed archive? I kept getting errors
>> using the unstable seed tarballs. A 'hg pull' of the whole
>> repository worked fine.
> 
> Yes, the seed repositories only work with 0.6b due to the directory
> name 'init.d' issue. We either need to update them or delete them.
> 
> Ian
> 
I always ran the James's script, but I got the error. Anyway I think we
should update the seed archive.  With the current seed archive, we don't
save network traffic significantly because a number of changes have been
made since then ;-).

Jun
---
Intel Open Source Technology Center