Yes, the following in samba-common.postinst:
ucf --three-way --debconf-ok "$NEWFILE" "$CONFIG"
ucfr samba-common "$CONFIG"
chmod a+r "$CONFIG"
results in:
Not replacing deleted config file /etc/samba/smb.conf
chmod: cannot access `/etc/samba/smb.conf': No such file or directory
If the file is deleted, it should probably reinstall a pristine version, rather than just "Not replacing" it and letting chmod fail :)
It's still something that shouldn't happen (/etc conffiles should be removed by purge, not manually) but given the number of updates that fail for this reason a more graceful handling of this corner case is definitely wanted.
Yes, the following in samba-common. postinst: smb.conf' : No such file or directory
ucf --three-way --debconf-ok "$NEWFILE" "$CONFIG"
ucfr samba-common "$CONFIG"
chmod a+r "$CONFIG"
results in:
Not replacing deleted config file /etc/samba/smb.conf
chmod: cannot access `/etc/samba/
If the file is deleted, it should probably reinstall a pristine version, rather than just "Not replacing" it and letting chmod fail :)
It's still something that shouldn't happen (/etc conffiles should be removed by purge, not manually) but given the number of updates that fail for this reason a more graceful handling of this corner case is definitely wanted.