Hi, (with random joe user/developer hat on) Russ Allbery <rra@debian.org> (18/01/2012): > However, it's not backward-compatible. If one was relying on the previous > behavior, this change will require switching away from the defaults. ouch. Doesn't seem like too good an idea for a stable upload. > Petter Reinholdtsen from DebianEdu requested this change make it into > stable as well, since it's causing problems for them (they set up accounts > in Kerberos and LDAP only by default). If they're directly affected by this, maybe it can be worked around on their side? > What do the stable release managers think? Is this something that would > be reasonable to do in stable? I think it does improve the package for > the majority use case, but it's a larger change in configuration than I > would normally propose for a stable update. If the majority use case improvement is worth it, maybe try and get on a middleground route: warn/ask through some debconf prompt about the behaviour change if it's an update, and go the preferred route (from your POV) if that's an installation? (Or prompt in all cases, maybe?) Mraw, KiBi.
Attachment:
signature.asc
Description: Digital signature