From: Taisuke Yamada <tyamadajp@list.rakugaki.org>
To: xen-devel@lists.xensource.com
Subject: Re: What version of hg does xenbits use?
Date: Wed, 31 Aug 2005 14:57:30 +0900 [thread overview]
Message-ID: <431546CA.5000600@list.rakugaki.org> (raw)
In-Reply-To: <4308A7A5.3080806@xensource.com>
Hi.
I just downloaded xen-unstable.tar.gz seed archive and still fails to
run "hg pull -u" using 0.6c toolkit.
Following is the (repeatable) trace I get. Is xenbit repository still
not ready, or is there anything I'm missing? I'm using mercirual 0.6c-1
package avaiable on Debian "sid". Thanks in advance.
tai@latte:/home/tai> cd /usr/local/src/xen-unstable.hg
tai@latte:/usr/local/src/xen-unstable.hg> ls
total 0
tai@latte:/usr/local/src/xen-unstable.hg> hg --version
Mercurial Distributed SCM (version 0.6c)
Copyright (C) 2005 Matt Mackall <mpm@selenic.com>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
tai@latte:/usr/local/src/xen-unstable.hg> hg pull -u
pulling from http://xenbits.xensource.com/xen-unstable.hg
searching for changes
adding changesets
adding manifests
adding file changes
added 868 changesets with 11154 changes to 1549 files
Traceback (most recent call last):
File "/usr/bin/hg", line 13, in ?
commands.run()
File "/usr/lib/python2.3/site-packages/mercurial/commands.py", line 1461, in run
sys.exit(dispatch(sys.argv[1:]))
File "/usr/lib/python2.3/site-packages/mercurial/commands.py", line 1571, in dispatch
return d()
File "/usr/lib/python2.3/site-packages/mercurial/commands.py", line 1556, in <lambda>
d = lambda: func(u, repo, *args, **cmdoptions)
File "/usr/lib/python2.3/site-packages/mercurial/commands.py", line 941, in pull
return update(ui, repo)
File "/usr/lib/python2.3/site-packages/mercurial/commands.py", line 1257, in update
return repo.update(node, allow=merge, force=clean)
File "/usr/lib/python2.3/site-packages/mercurial/hg.py", line 1734, in update
t = self.file(f).read(get[f])
File "/usr/lib/python2.3/site-packages/mercurial/hg.py", line 37, in read
t = self.revision(node)
File "/usr/lib/python2.3/site-packages/mercurial/revlog.py", line 244, in revision
rev = self.rev(node)
File "/usr/lib/python2.3/site-packages/mercurial/revlog.py", line 160, in rev
def rev(self, node): return self.nodemap[node]
KeyError: 'O\xf1\t\x95x\x19N\xcfG\xdd\xa6\xaa\xf7Z\xbf6\x98O\x96\xd9'
tai@latte:/usr/local/src/xen-unstable.hg>
>> xenbits uses 0.6b, the latest release version up until about 12 hours
>> ago when 0.6c was released. I'll upgrade xenbits to 0.6c over the
>> weekend.
>
> Just done this. Please report any problems directly to me. (And yes, the
> two blank changelog messages were an artifact of the upgrade.)
--
Taisuke Yamada <tyamadajp@spam.rakugaki.org>, http://rakugaki.org/
2268 E9A2 D4F9 014E F11D 1DF7 DCA3 83BC 78E5 CD3A
Message to my public address may not be handled in a timely manner.
For a direct contact, please use my private address on my namecard.
next prev parent reply other threads:[~2005-08-31 5:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 16:07 What version of hg does xenbits use? Anthony Liguori
2005-08-20 16:54 ` James Bulpin
2005-08-21 16:11 ` James Bulpin
2005-08-31 5:57 ` Taisuke Yamada [this message]
2005-08-31 12:31 ` James Bulpin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=431546CA.5000600@list.rakugaki.org \
--to=tyamadajp@list.rakugaki.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.