Hello Jelte, I discovered a low-priority problem when installing Unbound on Debian Lenny. It's package fights with bind9 (using the same ports, would that qualify as a package conflict? not sure) and the result is that the "start" script fails, leaving the package half-installed-and-in-conflict.
Removing bind9 was not even enough, because that package did not have the decency to terminate named in the removal process. In other words, the problem wouldn't even be solved by triggering a package conflict and thus having bind9 auto-removed upon installation of unbound. I thought you should know. Don't know Debian well enough yet to be able to give the full solution, but you might see a way. Cheers, -Rick _______________________________________________ Unbound-users mailing list [email protected] http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
