[Pkg-systemd-maintainers] Bug#719477: [Pkg-samba-maint] Bug#719477: Bug#719477: winbind 2:4.0.8+dfsg-1 fails to upgrade: systemd service file does not start the daemon

[Michael Biebl]

On Mon, Aug 12, 2013 at 02:11:13PM +0200, Ivo De Decker wrote:
> Hi,
> 
> On Mon, Aug 12, 2013 at 12:39:15PM +0200, Christian PERRIER wrote:
> > Well, as far as I know, systemd is not Debian's default init system so
> > far, so I don't think this bug deserves an RC severity.
> 
> The bug is actually in the systemd scripts upstream provides, as it doesn't
> use the PID path from waf/configure, but uses hardcoded /run instead.

Typically, service files shipped in upstream should use something like .service.in
files and some autofoo magic to replace the used paths with what has been
specified via configure. This is simple to do.

As for Debian, when shipping both systemd service files and LSB/SysV init scripts, you
should also make sure that the names align.

E.g. the SysV init scripts are named smbd and nmbd yet the upstream
service files are named nmb.service and smb.service. One can either
rename the service files are ship a symlink, to align the names.

If you are going to-reenable systemd support, feel free to contact us.
We are happy to help/review the changes.

Michael