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.
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 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.
A conflict is certainly a bad idea because there's nothing wrong with
running BIND and Unbound on the same machine. Some manual
configuration is required to make it work, but this is to be expected.