. . . doing a bit of research . . .
Others have had this error in the past. The following looks interesting.
Samba: subprocess post-installation script returned error exit status
1
<http://languor.us/samba-subprocess-post-installation-script-returned-error-exit-status-1>
The suggestion above was to "create a blank smb.conf in /etc/samba, then
purge and reinstall samba"
During the upgrade, it suggested I keep my current 'smb.conf' I
currently have the 'dcerpc' lines commented. Perhaps, I should
uncomment those since they call the OpenChange and 'mapiproxy' functions?
I inserted the 'dcerpc' comments as I was unable to login after a reboot
of my 'samba-ad-dc,' and the problem was perceived to be the calls to a
'broken' OpenChange (which applies to OpenChange before this upgrade)
Using a blank 'smb.conf' might not find my domain parameters to complete
the configuration.
If I purge my 'samba' db, will it delete all my user and machine
accounts? That's a worry!
Another suggestion might be to install an upgrade between my current
'samba' file and the Inverse package. I've been concerned about the
installed version since before starting this upgrade to Samba 4.1.18
Are there any suggestions? Has anyone else ran into this situation?
Should I ask the Samba list?
On 06/13/2015 12:01 PM, Steve Ankeny wrote:
Problems seem to start here . . .
dpkg: error processing package samba (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of winbind:
winbind depends on samba (= 2:4.1.18+dfsg-3~inverse1); however:
Package samba is not configured yet.
--
[email protected]
https://inverse.ca/sogo/lists
