> The package doesn't follow Debian policy for library package names. It should be libnss-hostname2.
No, it's an NSS module not a shared library - the soname shouldn't be part of the package name.
But as far as an FFe is concerned, I don't agree that libnss-myhostname is a technically sound approach, *period*; it works at cross-purposes to the existing Debian handling of the hostname being resolved to 127.0.1.1 via /etc/hosts. There should be a plan for aligning these, across *all* systems, not just desktop systems.
For my money, I believe the right answer is to ensure tools which update the system hostname also update /etc/hosts (via some common tool), and *not* add to the NSS overhead with this module.
> The package doesn't follow Debian policy for library package names. It should be libnss-hostname2.
No, it's an NSS module not a shared library - the soname shouldn't be part of the package name.
But as far as an FFe is concerned, I don't agree that libnss-myhostname is a technically sound approach, *period*; it works at cross-purposes to the existing Debian handling of the hostname being resolved to 127.0.1.1 via /etc/hosts. There should be a plan for aligning these, across *all* systems, not just desktop systems.
For my money, I believe the right answer is to ensure tools which update the system hostname also update /etc/hosts (via some common tool), and *not* add to the NSS overhead with this module.