Quoting Josip Rodin ([email protected]): > b) provide help for upgraders - add the line to the new default config > file, note the problem in NEWS.Debian, ...
Isn't this basically asking us to document each and every change to default settings for a given smb.conf parameter? We settled quite a while ago against having a Debian-crafted smb.conf file, with the choice of stayiong as close as possible to upstream defaults. Such inconvenience is a side effect of this. Indeed, good practice, for samba servers is mostly to check changes in smb.conf wrt upstream defaults. For my own servers, I always do the following before upgrading them, as a kind of non-regression test: Run "testparm" with the same smb.conf and both samba versions, then compare the output. This will easily enlight changes to upstream defaults and therefore allow me to carefully think about consequences for my users. Samba is too versatile and possible situations are too different to always guarantee a fully safe upgrade path. For the record, my own servers are still running lenny, with non-regression tests going on (we're currently just upgrading print servers).
signature.asc
Description: Digital signature
