Comment 4 for bug 1764327

Thanks (belatedly) for your comment, Faidon. I recognize that this is a complicated issue to resolve. However, at its root, I am unwilling to sign off on a package whose installation will cause dpkg and apt to exit non-zero on a default Ubuntu system. There are various ways this could be addressed; the package could bind 127.0.0.1 by default, or it could not autostart the service, or something else. But the package has been blocked in -proposed now for 3 years because of this issue, preventing any updates - including possible security updates of a security-sensitive package (a nameserver). So until this is resolved in some manner, I think the best course of action here is to remove the package, from both the release pocket and the -proposed pocket.

Leaving this bug report open, as a breadcrumb if/when there are further syncs of the package that have the same issue.