Traceback when reverting a subrepo using the latest unstable installer

5 views
Skip to first unread message

Angel Ezquerra

unread,
Sep 3, 2012, 5:46:28 PM9/3/12
to thg...@googlegroups.com
Hi,

Apologies if you get this (or a similar) email twice. I got a crash
while sending this email so I do not think that it ever got sent to
the list.

I get the following traceback whenever I try to revert a subrepo using
the latest unstable installer:

{{{
#!python
** Mercurial version (2.3+30-b0aad9fb87f9). TortoiseHg version
(2.4.3+21-c77727b4ecba)
** Command:
** CWD: C:\Program Files (x86)\TortoiseHg
** Encoding: cp1252
** Extensions loaded: graphlog, mq, rebase, convert, purge, hgban,
projrc, patchbomb
** Python version: 2.7.3 (default, Apr 10 2012, 23:24:47) [MSC v.1500
64 bit (AMD64)]
** Windows version: sys.getwindowsversion(major=6, minor=1,
build=7601, platform=2, service_pack='Service Pack 1')
** Processor architecture: x64
** Qt-4.8.0 PyQt-4.9.1
Traceback (most recent call last):
File "tortoisehg\hgqt\wctxactions.pyo", line 169, in runAction
File "tortoisehg\hgqt\wctxactions.pyo", line 294, in revert
File "mercurial\commands.pyo", line 5045, in revert
File "mercurial\cmdutil.pyo", line 1914, in revert
File "mercurial\subrepo.pyo", line 612, in revert
KeyError: 'all'

}}}

However, if I revert a subrepo when running thg from source I do not
get the traceback. Looking at the code I see that in wctxactions a
revertall dictionary is declared as follows:

revertopts = {'date': None, 'rev': '.', 'all': False}

It seems to me that revertopts is properly propagated downto
surepo.py, so I do not see how that 'all' key could be missing.

Any ideas?

Cheers,

Angel

Yuya Nishihara

unread,
Sep 4, 2012, 9:49:44 AM9/4/12
to thg...@googlegroups.com
That was recently fixed by d3cad1ca4a8b.

Regards,
Reply all
Reply to author
Forward
0 new messages