Package: python-logilab-common
Version: 0.16.1-2
Followup-For: Bug #355752

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The same hit me today during my system's upgrade procedure. I got:

Richte python-central ein (0.4.15) ...
Richte python2.3 ein (2.3.5-14) ...
pycentral: pycentral rtinstall: package python-logilab-common: already
  exists: /usr/lib/python2.3/site-packages/logilab/__init__.py
pycentral rtinstall: package python-logilab-common: already
  exists: /usr/lib/python2.3/site-packages/logilab/__init__.py
dpkg: Fehler beim Bearbeiten von python2.3 (--configure):
 Unterprozess post-installation script gab den Fehlerwert 1 zurück
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von python2.3-dev:

Then I looked into the directory and found:

ls -lA /usr/lib/python2.3/site-packages/logilab/
insgesamt 8
- -rw-r--r-- 1 root root   0 2006-03-03 01:45 __init__.py
- -rw-r--r-- 1 root root 132 2006-03-04 02:30 __init__.pyc
- -rw-r--r-- 1 root root 132 2006-03-08 03:12 __init__.pyo

After removing those files, installation process worked. I did not
upgrade from Sarge. It was a normal upgrade in Sid.

Daniel Leidert


- -- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (850, 'unstable'), (700, 'testing'), (550, 'stable'), (110, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15.08060320
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)

Versions of packages python-logilab-common depends on:
ii  python-central                0.4.15     register and build utility for Pyt
ii  python-xml                    0.8.4-4    XML tools for Python [dummy packag

python-logilab-common recommends no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEkK9Sdg0kG0+YFBERAnUlAJ9zVoG0HY3ogA7iqYsO1bHYYzCa0gCfdumx
+5v0KXkD/SrPTc4NRcXzuKw=
=JOVo
-----END PGP SIGNATURE-----


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

Reply via email to