On Sun, 2015-03-22 at 19:20 -0400, Chris Knadle wrote: > Christoph: there may be a lack of empathy in your response statements. > Please try to "put yourself in the user's shoes" -- the issue looks > very different from that perspective. [I'm likewise considering this > from the maintainer perspective.] Again, I don't see that Vincent wrote that this is a complete showstopper for him... even his bug title was about the modification of the config file, not about the new value itself. And you understand me wrong, if you think I'd have no empathy: There should be no reason for Vincent (or others) to get caught by that change by surprise, which I fully agree, but apart from that this is really such a small change that can be corrected in minutes. What would happen at other packages like apache when they go from 2.2 to 2.4 and config doesn't just work anymore? Or when the maintainer of gitolite finally gives up upon 2.x and replaces the "gitolite" with the "gitolite3" package? These things require considerable work by the admin,... are people then going to start a war because something changes? What about OpenSSH, when they finally drop/disable unsafe alogs? I'm not discussing for that particular AcceptEnv/SendEnv issue so enthusiastically because I think it is so important by itself - but rather as this could be taken as precedent for other changes (like dropping unsafe algos) in the future. Best wishes, Chris.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature