On Mon, 14 Dec 2009 09:16:42 -0500 Sam Hartman <hartm...@debian.org> wrote:
> 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. No matter what happened exactly in my case, I see it quite likely that people break their system. The only thing you have to do is to install a package from testing/unstable on a lenny system with a dependency to libk5crypto3 and then uninstall it again. Libk5crypto3 will get uninstalled as well, as it is marked as an automatic dependency and it's good bye for your remote system. Cheers, harry
signature.asc
Description: PGP signature
