sudo (1.7.2p1-2) UNRELEASED; urgency=low
- * working on substitution variables in man pages
+ * move to source format 3.0 (quilt) and restructure changes as patches
+ * fix unprocessed substitution variables in man pages, closes: #557204
+ * apply patch from Neil Moore to fix Debian-specific content in the
+ visudo man page, closes: #555013
-- Bdale Garbee <bdale@gag.com> Fri, 20 Nov 2009 07:31:30 -0700
--- /dev/null
+sudo-1.7.2p1-visudo-manpage-fix.diff
--- /dev/null
+--- sudo-1.7.2p1/visudo.pod 2008-11-15 13:34:01.000000000 -0500
++++ sudo-1.7.2p1-manpage/visudo.pod 2009-11-07 18:54:00.841321731 -0500
+@@ -39,15 +39,18 @@
+
+ There is a hard-coded list of editors that B<visudo> will use set
+ at compile-time that may be overridden via the I<editor> I<sudoers>
+-C<Default> variable. This list defaults to the path to L<vi(1)> on
+-your system, as determined by the I<configure> script. Normally,
++C<Default> variable. On Debian systems, this list defaults to
++/usr/bin/editor, which is meant to be a system-wide default editor
++chosen through the alternatives system. Normally,
+ B<visudo> does not honor the C<VISUAL> or C<EDITOR> environment
+ variables unless they contain an editor in the aforementioned editors
+-list. However, if B<visudo> is configured with the I<--with-enveditor>
++list. However, if B<visudo> is configured with the I<--with-env-editor>
+ option or the I<env_editor> C<Default> variable is set in I<sudoers>,
+ B<visudo> will use any the editor defines by C<VISUAL> or C<EDITOR>.
+ Note that this can be a security hole since it allows the user to
+ execute any program they wish simply by setting C<VISUAL> or C<EDITOR>.
++Despite this potential risk, sudo on Debian is compiled with the
++I<--with-env-editor> flag.
+
+ B<visudo> parses the I<sudoers> file after the edit and will
+ not save the changes if there is a syntax error. Upon finding
--- /dev/null
+3.0 (quilt)
.PP
There is a hard-coded list of editors that \fBvisudo\fR will use set
at compile-time that may be overridden via the \fIeditor\fR \fIsudoers\fR
-\&\f(CW\*(C`Default\*(C'\fR variable.
-On Debian systems, this list defaults to /usr/bin/editor, which is meant to
-be a system-wide default editor chosen through the alternatives system.
-Normally, \&\fBvisudo\fR does not honor the \f(CW\*(C`VISUAL\*(C'\fR or
-\f(CW\*(C`EDITOR\*(C'\fR environment
+\&\f(CW\*(C`Default\*(C'\fR variable. This list defaults to the path to \fIvi\fR\|(1) on
+your system, as determined by the \fIconfigure\fR script. Normally,
+\&\fBvisudo\fR does not honor the \f(CW\*(C`VISUAL\*(C'\fR or \f(CW\*(C`EDITOR\*(C'\fR environment
variables unless they contain an editor in the aforementioned editors
list. However, if \fBvisudo\fR is configured with the \fI\-\-with\-enveditor\fR
option or the \fIenv_editor\fR \f(CW\*(C`Default\*(C'\fR variable is set in \fIsudoers\fR,
\&\fBvisudo\fR will use any the editor defines by \f(CW\*(C`VISUAL\*(C'\fR or \f(CW\*(C`EDITOR\*(C'\fR.
Note that this can be a security hole since it allows the user to
execute any program they wish simply by setting \f(CW\*(C`VISUAL\*(C'\fR or \f(CW\*(C`EDITOR\*(C'\fR.
-Despite this potential risk, sudo on Debian is compiled with the
-\fI\-\-with\-enveditor\fR flag.
.PP
\&\fBvisudo\fR parses the \fIsudoers\fR file after the edit and will
not save the changes if there is a syntax error. Upon finding