tags 421066 +wontfix thanks On Thu, 2007-04-26 at 10:32 +0200, Philippe Teuwen wrote: > Probably you've good reasons to drop default support of sudo group but > *please* use debconf to prompt the user and tell him, it's only when I read > the newly installed /usr/share/doc/sudo/NEWS.Debian.gz that I understood > what happened.
Sorry you got caught by this. For the vast majority of users, this is a no-op, so making everyone stop for a debconf interrupt on upgrade seemed over the top at the time I was deciding how to handle the change. I'm peronally a really big fan of apt-listchanges on the machines I manage that have this degree of importance, because it gives you a chance to review all the news items and changelog entries that are relevant before you pull the trigger on an upgrade, and because the email it can generate provides something akin to an audit trail for what was updated when that I've found useful on several occasions. While I realize it won't help you retroactively with this problem, this is a package you might appreciate in the future. > I graded this report as important because of the worries it can cause to > admins > with similar setup. Fair enough. There isn't a lot I can do a this point other than leave the bug open for a while, though, as etch is now stable and I doubt a fix for this would be deemed important enough to include in a stable update. > PS: now I've taken measures to ensure safe root access when sudo is not > working... Probably a good idea for any mission-critical system, but my apologies anyway as I understand the stress losing root access to a server can cause! Bdale -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
