On Monday 15 of July 2019 01:04:24 Mike Bird wrote:
> On Sun July 14 2019 15:34:15 Felix Miata wrote:
> > insserv: FATAL: service rpcbind is missed in the runlevels 2 3 4 5 to
> > use service nfs-common
>
> (1) If you don't really need NFS you could try purging it.
>
>
> (2) Otherwise let's check that you have the right Buster versions:
>
> $ (dpkg -l rpcbind; dpkg -l nfs-common) | grep '^ii'
> ii  rpcbind        0.2.3-0.6    amd64        converts RPC program
> numbers into universal addresses
> ii  nfs-common     1:1.3.4-2.1  amd64        NFS support files common to
> client and server
>
>
> (3) If the versions are correct take a look at both relevant files:
>
> $ head /etc/init.d/rpcbind
> #!/bin/sh
> #
> # start/stop rpcbind daemon.
>
> ### BEGIN INIT INFO
> # Provides:          rpcbind
> # Required-Start:    $network $local_fs
> # Required-Stop:     $network $local_fs
> # Default-Start:     S
> # Default-Stop:      0 1 6
>
> $ head /etc/init.d/nfs-common
> #!/bin/bash
>
> ### BEGIN INIT INFO
> # Provides:          nfs-common
> # Required-Start:    $portmap $time
> # Required-Stop:     $time
> # Default-Start:     S
> # Default-Stop:      0 1 6
> # Short-Description: NFS support files common to client and server
> # Description:       NFS is a popular protocol for file sharing across
>
>
> (4) If yours are different try reinstalling them, or purging and
> reinstalling them, or as a last resort editing them to look like the
> above.
>
>
> --Mike
>

In any case, I thank to both for a useful result! Though somewhat strange, 
tdm-trinity fails but not its own guilty. Now at least we know what needs 
to treat.

Cheers
-- 
Sl�vek