Hello,
I appreciate that you are having similar problems with winbind, but
let's please use a new bug for that. This one here had a clear error in
the configuration file.
Steven, I would appreciate a new bug with details of your case, in
particular, the config file and the ordering of events that are leading
to a postinst failure. I've seen failures in automated deploys where
winbind is started before being correctly joined to a domain, or
something of the sort. We should definitely find a way to streamline
that, if this is the case you are describing.
The bits you mentioned are added by debhelper automatically to any package
shipping systemd and/or sysv scripts. This is what is in the samba source
package regarding winbind.postinst, for example:
"""
#! /bin/sh
set -e
getent group winbindd_priv >/dev/null 2>&1 ||
addgroup --system --force-badname --quiet winbindd_priv
winbindd_privileged_socket_directory='/var/lib/samba/winbindd_privileged'
mkdir -pv "$winbindd_privileged_socket_directory"
chgrp -c winbindd_priv "$winbindd_privileged_socket_directory"
chmod -c 0750 "$winbindd_privileged_socket_directory"
#DEBHELPER#
"""
Here, #DEBHELPER# is the special text that is replaced by debhelper with
other shell snippets as needed, and is what you probably saw.
Regarding systemd and sysv, I agree that it is confusing to ship both. I
have actually seen packages that also ship an upstart snippet along
those two.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787834
Title:
package winbind 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 failed to
install/upgrade: installed winbind package post-installation script
subprocess returned error exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1787834/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
