When I first installed scanbd, I found that the systemd unit could not
start, because inetd was already listening on the scanbd port.

It seems to me that scanbd should only configure one of systemd or
inetd when it installs. In particular, scanbd depends on openbsd-inetd
| inet-superserver, so it forces the installation of some inetd, and
this will always happen.

In my case, I have inetd installed anyway, but only for one or two
legacy services that I have not yet migrated to a systemd
configuration.

Maybe it would be reasonable only to add active inetd configuration on
systems that aren't running systemd?

(Some more general feedback: I see in README.Debian for this package
that "a lot of work went into smoothening the scanbd experience on
Debian". For me, scanbd was a lot of work to get working; so, I am
very grateful for this work, but it seems there is more to do, in
particular to fix upstream bugs. If I can find time, I will look into
this myself; meanwhile, thanks very much for the packaging work,
without which I'm sure I would have given up altogether.)