Your message dated Sat, 13 Aug 2011 17:51:05 -0700
with message-id 
<caek95gfe9w_ix31redxpdvge7+fg4nl1urwa0ejzf-vt6wx...@mail.gmail.com>
and subject line Re: Bug#636676: tortoisehg: TortoiseHG cannot start (no module 
named color)
has caused the Debian Bug report #636676,
regarding tortoisehg: TortoiseHG cannot start (no module named color)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
636676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636676
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tortoisehg
Version: 2.1.1-1
Severity: important

Problem is similar to this bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635591
but now stacktrace show other problems:

{{{
#!python
** Mercurial version (1.9.1).  TortoiseHg version (2.1.1)
** Command: status
** CWD: /home/dasm/apps/filmaster/reloaded/film20
** Extensions loaded:
** Python version: 2.6.7 (r267:88850, Aug  3 2011, 11:33:52) [GCC 4.6.1]
** Qt-4.7.3 PyQt-4.8.3
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/tortoisehg/hgqt/run.py", line
474, in __call__
    self._installtranslator()
  File "/usr/lib/python2.6/dist-packages/tortoisehg/hgqt/run.py", line
512, in _installtranslator
    t.load('qt_' + i18n.language, qtlib.gettranslationpath())
  File "/usr/lib/python2.6/dist-packages/mercurial/demandimport.py",
line 75, in __getattribute__
    self._load()
  File "/usr/lib/python2.6/dist-packages/mercurial/demandimport.py",
line 47, in _load
    mod = _origimport(head, globals, locals)
  File "/usr/lib/python2.6/dist-packages/tortoisehg/hgqt/qtlib.py",
line 22, in <module>
    from hgext.color import _styles
  File "/usr/lib/python2.6/dist-packages/mercurial/demandimport.py",
line 109, in _demandimport
    mod = _origimport(name, globals, locals)
ImportError: No module named color

}}}

Problem exist wherever I try to run thg

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages tortoisehg depends on:
ii  mercurial                     1.9.1-1    scalable distributed version contr
ii  python                        2.6.7-2    interactive high-level object-orie
ii  python-gobject                2.28.6-4   Python bindings for the GObject li
ii  python-qscintilla2            2.4.5-1    Python bindings for QScintilla 2
ii  python-qt4                    4.8.3-3    Python bindings for Qt4
ii  python2.6                     2.6.7-4    An interactive high-level object-o
ii  python2.7                     2.7.2-4    An interactive high-level object-o

Versions of packages tortoisehg recommends:
ii  libjs-jquery                  1.6.2-1    JavaScript library for dynamic web
ii  python-iniparse               0.4-2.1    Module to access and modify config
ii  python-pygments               1.4+dfsg-2 syntax highlighting package writte

Versions of packages tortoisehg suggests:
pn  tortoisehg-nautilus           <none>     (no description available)

-- no debconf information



--- End Message ---
--- Begin Message ---
2011/8/9 Dariusz Śmigiel <[email protected]>:
>> And also that you have /usr/lib/python2.6/dist-packages/hgext/color.py
> Strange, because I have color.py inside this folder. I thought that
> maybe problem exists because I use virtualenv.

I am not familiar with virtualenv...

> After your email once more time I've checked everything. I've
> reinstalled mercurial, mercurial-common and tortoisehg and now it
> works. I don't know where was problem.
> Sorry for the confusion.

No problem, closing the bug as it was likely due to some package in a
half-installed state.
Please reopen if it happens again.

Thanks,
Ludovico


--- End Message ---

Reply via email to