RM & blacklist socket-activate duplicated functionality

[Dimitri John Ledkov]

socket-activate duplicates the functionality and implementation of systemd-socket-activate utility shipped by default on all ubuntu architectures.

Lacks documentation (i.e. does not have --help) and has incompatible set of options.

It fails to build from source with testsuite errors.

Claims to have little dependencies, however depends on the python3 which overall has slower startup performance than C implementation of systemd-socket-activate.

This package, in its current form, should not exist in Ubuntu.

[Steve Langasek (vorlon)]

I've removed the source package from groovy:

Removing packages from groovy-proposed:
 socket-activate 0.1-2 in groovy
Comment: FTBFS, not useful on Ubuntu; LP: #1882091
1 package successfully removed.

However I'd like to get clarification on the blacklisting. Is this package part of the broader Debian story about how to make packages function without modification in docker containers? If someone did get this to build, would it still be useful there?

[Dimitri John Ledkov (xnox)]

systemd-socket-activate is a standalone utility usable to socket activate daemons standalone without systemd manager running.

systemd-socket-activate is perfectly usable inside docker containers for single-process execution without a full/traditional init system.

[Steve Langasek (vorlon)]

thanks for the clarification. added to the blacklist.