Excuse me for the long time without an answer. Blu dijo [Mon, May 04, 2009 at 04:34:29PM -0400]: > > 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.
Umm... Quite strange, really. Even if it were only half-installed, the installation process should always be able to pick up where it left. In which state are each of Cherokee's packages? (dpkg -l *cherokee*) - More specifically, does any of the result lines does not start with "ii". In any case, try reconfiguring them (i.e. «dpkg --reconfigure libcherokee-config0») > 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. I guess this might have stemmed from an interrupted installation or something like that... > > 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. To be honest, I am a complete newbie to the python-support scripts, I only followed the recipes to get them working. What does /usr/share/python-support/libcherokee-config0.private include? Of course, the installation will create it - It should contain a listing of Python files, all under /usr/share/cherokee/admin - python-support basically takes care of byte-compiling them for your currently installed Python release (and removing the .pyc files upon package removal). It does not need to be a directrory - look at the other entries you have under /usr/share/python-support/, some are directories and some are not. From what I can gather, the packages whose files are named *.private are those (like Cherokee) shipping Python modules meant for internal use, in /usr/share/<pkgname>. In any case - If the problem is still happening, I would suggest you to completely purge all Cherokee packages (I don't know what can be botched!) and reinstalling them. How to purge them, you ask? Well... Please don't get used to hand-modifying these files, but in case it is needed to get your system back in shape (and if the only package causing breakage is libcherokee-config0), you can just remove /var/lib/dpkg/info/libcherokee-config0.prerm - Its only purpose is to run python-support. Once you can successfully purge the package, remove /usr/share/cherokee/admin/*.pyc and you should be set. If this solves your problem, please try installing/purging/installing - no problems should remain. And the Python files should be properly managed by python-support. Greetings, -- Gunnar Wolf - gw...@gwolf.org - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
