Subject says it all. If we don't do anything and don't do anything *quickly* we will be overloaded with identical bug reports.
In first reaction, I'm really angry at upstream for them creating a panic on wrong settings but it seems that our only solution is to forcibly change the wrong settings of our users on upgrades. So, who feels like doing this? Do we do it silently without prompting? This is, strictly speaking, non policy compliant....but who wants a package that will panic after an upgrade? If we don't, we need to create a debconf template, probably show it at critical priority, asking for permission to replace "passdb backend = tdbsam guest" by "passdb backend = tdbsam". With either "True" or "False" as default. "True" as default would mean we would, in some cases, change a user setting silentily.... "False" as default would mean that we would leave some users with the wrong settings Steve, you're the Wise Man here....please give your advice. Peter, Noèl, Eloy, others, feel free to do so as well. I personnally vote for *forcibly* change the setting. We MUST fix this soon, or we won't survive...:) --
signature.asc
Description: Digital signature
