On Mon, Jul 6, 2009 at 3:08 PM, Steve Borho<st...@borho.org> wrote:
> On Mon, Jul 6, 2009 at 1:11 AM, TK Soh<teekay...@gmail.com> wrote:
>> On Mon, Jul 6, 2009 at 4:50 AM, Steve Borho<st...@borho.org> wrote:
>>>> I am using 0.8's hgtk via symlink on Fedora 9, but am getting the
>>>> "icon not found" messages too. I was not getting this error error
>>>> before that (not sure which version I was using). I checked  hgtk's
>>>> wiki page, but not special notes on the symlink approach. Any
>>>> pointers?
>>>
>>> Look for thgutil/config.py*, and delete anything you find.  Setup.py
>>
>> Somehow I had to remove everything and do hg co -C to get it to work.
>> Anyway, it seemed to fix the problem. Thanks.
>>
>>> is building this file because you need it if you are installing
>>> tortoisehg under /usr.  Unfortunately it does this even if you just
>>> run something like 'python setup --version'.
>>>
>>> I almost checked in a workaround for it today, but I didn't like the
>>> hack so I'm going to think about it a bit more.
>
> Ah, a couple of other of people have seen this as well.  When you
> update your live repo between 0.7 and 0.8 it may leave some old pyc
> files in place that confuse the new code.  I haven't looked into the
> exact cause of the conflict, but what I recommend for people updating
> a live repo is to do:
>
> hg update null
> rm -rf hggtk tortoise thgutil icons
> hg update tip

Just curious, would 'rm -rf ...' + 'update -C' be enough?

TK

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have 
the opportunity to enter the BlackBerry Developer Challenge. See full prize 
details at: http://p.sf.net/sfu/blackberry
_______________________________________________
Tortoisehg-discuss mailing list
Tortoisehg-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss

Reply via email to