I'm very confused. I've looked over your logs and your package dependencies and I cannot figure out how you managed to get into this state.
It's possible that one version of jabberd2 was built against a newer Kerberos and a later version ]was built against an older Kerberos. If that's the case, then the problem is unlikely to happen for others in the future. Alternatively, though, it might be something I don't understand at all, which is concerning because I can do little to predict how many people it will affect. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
