block 500266 by 478685 thanks Hi,
I'm very ashamed (and have no excuse!) for taking so long in replying to this bug report. The workaround (and, yes, I know it is not an _acceptable_ workaround - But I promise to push upstream into giving me a way to fix this! ;-) ) is to deinstall and reinstall Cherokee, instead of upgrading it. This happens because of an oversight I noticed a bit too late - 0.6.1 introduced the cherokee-admin interface and libcherokee-config0 library, but I didn't actually move the required bits into the libcherokee-config0 package until 0.8.1-1. Now, as libcherokee-server0 and libcherokee-config0 depend on each other (and that's the issue reported in #478685), and the same file exists in libcherokee-server0 <= 0.7.2-4 and libcherokee-config0 >= 0.8.1-1, the upgrade fails. #478685 was filed quite a bit ago, but I didn't regard it as important enough. And #500266, which should be quite prioritary, didn't get any attention because I just missed it! :-@ Anyway, I don't have an answer yet - but I promise to have it soon. Thanks for the patience, and sorry again. -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF
pgp6hiDfTu7uK.pgp
Description: PGP signature
