Package: python-opensync
Version: 0.39-1
Severity: normal
While updating from 0.22-4+b1 to 0.39-1 I got the following:
Unpacking replacement python-opensync ...
Processing triggers for man-db ...
Processing triggers for python-support ...
Compiling /usr/lib/pymodules/python2.5/opensync.py ...
Sorry: IndentationError: ('unexpected indent',
('/usr/lib/pymodules/python2.5/opensync.py', 597, 19, '
/*\n'))
Setting up librrds-perl (1.4.2-1) ...
Setting up python-opensync (0.39-1) ...
Processing triggers for python-support ...
Compiling /usr/lib/pymodules/python2.5/opensync.py ...
Sorry: IndentationError: ('unexpected indent',
('/usr/lib/pymodules/python2.5/opensync.py', 597, 19, '
/*\n'))
Compiling /usr/lib/pymodules/python2.6/opensync.py ...
Sorry: IndentationError: ('unexpected indent',
('/usr/lib/pymodules/python2.6/opensync.py', 597, 19, '
/*\n'))
I don't know if it means anything as I'm currently not really using
opensync.
Please reassign/reclassify severance as needed.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (101, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.31-sdinet52-aurora (SMP w/2 CPU cores)
Locale: LANG=en_US.ISO-8859-1, LC_CTYPE=de_DE.ISO-8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages python-opensync depends on:
ii libc6 2.10.2-5 Embedded GNU C Library: Shared lib
ii libglib2.0-0 2.22.4-1 The GLib library of C routines
ii libopensync1exp7 0.39-1 Synchronisation framework for emai
ii libpython2.6 2.6.4-4 Shared Python runtime library (ver
ii libsqlite3-0 3.6.21-2 SQLite 3 shared library
ii libxml2 2.7.6.dfsg-2 GNOME XML library
ii libxslt1.1 1.1.26-1 XSLT processing library - runtime
ii python 2.5.4-9 An interactive high-level object-o
ii python-support 1.0.6 automated rebuilding support for P
ii python2.5 2.5.4-3 An interactive high-level object-o
python-opensync recommends no packages.
python-opensync suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]