On Sun, May 03, 2009 at 08:46:38PM -0500, Gunnar Wolf wrote: > Umh, quite weird... > > Leonel Nunez dijo [Sun, May 03, 2009 at 05:37:03PM -0600]: > > > Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) > > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > > > Shell: /bin/sh linked to /bin/bash > > > > > > Versions of packages libcherokee-config0 depends on: > > > ii libc6 2.9-8 GNU C Library: Shared > > > libraries > > > ii libcherokee-base0 0.98.1-1 Cherokee web server - Base > > > librari > > > ii libcherokee-client0 0.98.1-1 Cherokee web server - Client > > > libra > > > ii libcherokee-server0 0.98.1-1 Cherokee web server - Server > > > libra > > > ii libssl0.9.8 0.9.8g-16 SSL shared libraries > > > ii python 2.5.4-2 An interactive high-level > > > object-o > > > > > > libcherokee-config0 recommends no packages. > > > > > > libcherokee-config0 suggests no packages. > > > > Can you please Upgrade your system ? > > We are on kernel 2.6.26-2 and many other packages > > Umh, that would make no difference, I fear. I just checked and, except > for the kernel version, his system libraries and packages are all the > same version I am (except for libc6, which I currently have at > 2.9-7). The only strange thing I see is that the report seems to be > for a Cherokee 0.99.11 -> 0.99.13 upgrade, while the reported Cherokee > libraries are all at 0.98.1.
It could be a dependency problem. I started the upgrade (by means of apt-get dist-upgrade) with a cherokee version 0.98.1-1, but it never finished. Maybe it left a mix of new and old versions. > > 'y' (you don't provide a name to be addressed by), all of Cherokee's > components are designed to work at the same version levels; I don't > have the strict relationships set except for the main Cherokee package > itself (which depends on exactly the same version of the libraries > than the one installed) in order to prevent dependency cycles and > similar conditions which can prevent package updates in weird > situtations. Please tell me how were you trying to update - Was it > through apt/aptitude, or installing straight via dpkg? Did you try > installing the other corresponding packages as well? As I said, I use apt-get dist-upgrade. I assume this should pull dependencies. If not, I have to figure out first a way of get rid of the offending pakage to be able to install other packages, or maybe I'll go with plain dpkg if nothing else works. > > But on the other hand... > > > Can you please provide your python-support version ? > > (...) > > > Upgrading the package, I get: > > > > > > ===== > > > Preparing to replace libcherokee-config0 0.99.11-1 (using > > > ..../libcherokee-config0_0.99.13-1_i386.deb) ... > > > Usage: update-python-modules [-v] [-c] package_directory [...] > > > update-python-modules [-v] [-c] package.dirs [...] > > > update-python-modules [-v] [-a|-f|-p] > > > > > > update-python-modules: error: > > > /usr/share/python-support/libcherokee-config0.private is not a directory > > > dpkg: warning - old pre-removal script returned error exit status 2 > > > dpkg - trying script from the new package instead ... > > > Usage: update-python-modules [-v] [-c] package_directory [...] > > > update-python-modules [-v] [-c] package.dirs [...] > > > update-python-modules [-v] [-a|-f|-p] > > > > > > update-python-modules: error: > > > /usr/share/python-support/libcherokee-config0.private is not a directory > > > dpkg: error processing > > > /var/cache/apt/archives/libcherokee-config0_0.99.13-1_i386.deb (--unpack): > > > subprocess new pre-removal script returned error exit status 2 > > > Usage: update-python-modules [-v] [-c] package_directory [...] > > > update-python-modules [-v] [-c] package.dirs [...] > > > update-python-modules [-v] [-a|-f|-p] > > > > > > update-python-modules: error: > > > /usr/share/python-support/libcherokee-config0.private is not a directory > > > dpkg: error while cleaning up: > > > subprocess post-installation script returned error exit status 2 > > > Errors were encountered while processing: > > > /var/cache/apt/archives/libcherokee-config0_0.99.13-1_i386.deb > > > E: Sub-process /usr/bin/dpkg returned an error code (1) > > This does seem even stranger. The files in /usr/share/python-support > should exist since Cherokee 0.7.2-4, where the python-support was > included. I even tried to move /usr/share/python-support/libcherokee-config0.private out of the way, but the installation keeps recreating it, and not as directory as the script seems to require. Sorry for not being more helpful, I'm short of time right now, maybe tonigh I will investigate further. -- Blu. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
