Package: bug-triage
Version: 0.2.2-1
Severity: important
File: /usr/bin/bug-triage

bug-triage fails to start because it assumes that none of the python modules
in sys.path is called ui. I have installed reportbug-ng which doesn't qualify
its modules in a separate namespace, and one of those happens to be called ui
(I will also file a bug report for reportbug-ng.)

Please consider either using something like python-support, or place the
bug-triage modules in /usr/share/bug-triage/bug_triage (and instead import
bug_triage.ui.gtk.core).


$ bug-triage
Traceback (most recent call last):
  File "/usr/bin/bug-triage", line 32, in <module>
    import ui.gtk.core
ImportError: No module named gtk.core


$ python
Python 2.5.2 (r252:60911, Aug  8 2008, 09:22:44) 
[GCC 4.3.1] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys, os
>>> [p for p in sys.path if os.path.exists(p + "/ui")]
['/var/lib/python-support/python2.5']


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-1-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bug-triage depends on:
ii  python                        2.5.2-2    An interactive high-level object-o
ii  python-btsutils               0.3-1      Python module to interact with deb
ii  python-bzutils                0.2-1      Python module to interact with bug
ii  python-glade2                 2.12.1-6   GTK+ bindings: Glade support
ii  python-gtk2                   2.12.1-6   Python bindings for the GTK+ widge
ii  python-support                0.8.5      automated rebuilding support for P
ii  xdg-utils                     1.0.2-6    desktop integration utilities from

bug-triage recommends no packages.

bug-triage suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to