Package: config-manager
Version: 0.3-2
Severity: grave
Justification: renders package unusable

Hello,

I think some files are missing from the package:

$ cm
Traceback (most recent call last):
  File "/usr/bin/cm.py", line 27, in ?
    from config_manager import main
  File "/usr/lib/python2.4/site-packages/config_manager/__init__.py", line 24, 
in ?
    import config_manager.implementations
ImportError: No module named implementations
            
Confirmation:
$ dpkg -L config-manager
/.
/usr
/usr/bin
/usr/bin/cm
/usr/bin/cm.py
/usr/bin/cm.bin
/usr/lib
/usr/lib/python2.4
/usr/lib/python2.4/site-packages
/usr/lib/python2.4/site-packages/config_manager
/usr/lib/python2.4/site-packages/config_manager/__init__.py
/usr/lib/python2.4/site-packages/config_manager/optparse.py
/usr/share
/usr/share/doc
/usr/share/doc/config-manager
/usr/share/doc/config-manager/README
/usr/share/doc/config-manager/HOWTO
/usr/share/doc/config-manager/sample-config.txt
/usr/share/doc/config-manager/README.Debian
/usr/share/doc/config-manager/copyright
/usr/share/doc/config-manager/changelog.Debian.gz

Regards,

Olivier     

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages config-manager depends on:
ii  bzr                         0.7-3        bazaar-ng, the next-generation dis
ii  libc6                       2.3.6-7      GNU C Library: Shared libraries
ii  libgcc1                     1:4.1.0-1+b1 GCC support library
ii  libstdc++6                  4.1.0-1+b1   The GNU Standard C++ Library v3
ii  pybaz                       1.5pre1-2    python bindings for the bazaar rev
ii  python2.4                   2.4.2-2      An interactive high-level object-o

config-manager recommends no packages.

-- no debconf information


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

Reply via email to