[ Sorry, I have been really not responsive enough regarding this
report :-( ]
Umh, this is quite strange - dr4ke's message reports this bug stems
from having different versions of Cherokee's libraries. Now, going
over the binary packages, all dependencies are declared with explicit
«(= ${binary:Version})».
Hmmm... But taking a deeper look into it, I think I got it nailed: All
of the _dependency_ relations were versioned, but not the
recommended/suggested ones. So, if you were explicitly upgrading from
a package in Stable to a package in Testing, dpkg didn't pull in any
but the explicitly declared dependencies.
I added versioned relations to all of the suggested packages, and
added a Conflicts: line on libcherokee-server0 to (<<
${binary:Version}) on all of them. I _think_ it will work - I will
upload the package closing this bug soon (I want first to check if
there is any other bug I can work on). Of course, please reopen the
bug if you don't feel it has been fixed.
--
Gunnar Wolf • gw...@gwolf.org • (+52-55)5623-0154 / 1451-2244
signature.asc
Description: Digital signature
