On Wed, Dec 2, 2009 at 10:03 AM, Steve Borho <st...@borho.org> wrote: > On Wed, Dec 2, 2009 at 9:48 AM, Steve Borho <st...@borho.org> wrote: >> On Wed, Dec 2, 2009 at 8:42 AM, Adrian Buehlmann <adr...@cadifra.com> wrote: >>> On 02.12.2009 07:02, Steve Borho wrote: >>>> TortoiseHg 0.9.1 is a minor bugfix and "polish" release. Users with >>>> 0.9 are recommended to upgrade. >>>> >>>> http://bitbucket.org/tortoisehg/stable/wiki/ReleaseNotes >>>> >>>> The Windows installer for TortoiseHG 0.9.1 includes Mercurial 1.4.1 >>>> >>>> Warning: over the weekend we discovered the nightly build packages >>>> have begun popping up an error window when you install them. This new >>>> 0.9.1 installer also exhibits this behavior. Do not be surprised if >>>> you see a dialog box open up while files are being copied into place. >>>> The dialog text will be: >>>> >>>> Internal error: Expression error 'Runtime Error (at 1:229): >>>> Internal error: Unknown constant "1" >>>> >>> >>> Offhand I would say this might be caused by your >>> >>> http://bitbucket.org/tortoisehg/stable/changeset/b28a3b3dc018/ >>> >>> which did >>> >>> diff --git a/contrib/win32/mercurial.ini b/contrib/win32/mercurial.ini >>> --- a/contrib/win32/mercurial.ini >>> +++ b/contrib/win32/mercurial.ini >>> @@ -99,6 +99,7 @@ extdiff = >>> ; Extra extensions bundled with TortoiseHg >>> ;fold = >>> ;hgcr-gui = >>> +;schemes = >>> >>> ; To use cleverencode/cleverdecode, you must enable win32text extension >>> ; >>> @@ -195,3 +196,11 @@ opts.vdiff = $parent1 $child $parent2 >>> >>> [keywordmaps] >>> ; See documentation for examples >>> + >>> +; The schemes extension must be enabled to use one of these shortcuts. >>> +; See http://mercurial.selenic.com/wiki/SchemesExtension >>> +[schemes] >>> +;bb = http://bitbucket.org/ >>> +;bb+ssh = ssh://h...@bitbucket.org/ >>> +;gcode = http://{1}.googlecode.com/hg/ >>> +;py = http://code.python.org/hg/ >>> >>> >>> on line 26 you have >>> >>> ssh = "{app}\TortoisePlink.exe" -ssh -2 >>> >>> >>> so I guess there could be some conflict in syntax and semantics bout {var} >>> >>> (but I haven't verified this theory) >> >> That is a pretty good theory. I remember now I had similar problems >> when I tried to document the keyword extension, which also uses curly >> braces. >> >> The good news is that schemes was pulled into hgext soon after I >> pulled it into the TortoiseHg installer. So I can just remove those >> lines from the stock ini file. > > > This problem broke variable expansion for the entire Mercurial.ini > file, which in turn breaks ssh and visual diff. I'm going to have to > create another 0.9.1 installer tonight. If you have installed 0.9.1 > already, you can work around the problem by replacing {app} with the > path to your install directory. Or you can use a backup Mercurial.ini > from the backups folder if this was an upgrade.
I've just uploaded a TortoiseHg 0.9.1.1 package up on Bitbucket. It resolves the known installer issues and fixes one other bug that was reported yesterday. I've also removed the 0.9.1 installer to prevent people from downloading it by accident. If anyone is keeping URLs to TortoiseHg packages, please update to the 0.9.1.1 installer. I'll take care of the Mercurial Wiki shortly. -- Steve Borho ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Tortoisehg-discuss mailing list Tortoisehg-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
