Well, you could try --mode=standard to bypass the prompt in the meantime until I upload a fix.
Chris On 5/18/05, Peter S Galbraith <[EMAIL PROTECTED]> wrote: > Package: reportbug > Version: 3.12 > Severity: important > > Hi, > > This refers to http://bugs.debian.org/309598 > > If reportbug is started without an ~/.reportbugrc file, an interactive > prompt may appear concerning vi: > > You appear to be using the "vi" editor, which is not suited for new users. > You > probably want to change this setting by using "update-alternatives --config > editor" as root. Do you want to continue? [y|N|q|?]? > > This occurs even when the command line option --template is used, which > should be completely non-interactive. Unfortunately, the current > behaviour breaks debian-el's `M-x debian-bug' Emacs command which calls > reportbug like so: > > $ reportbug --template -T none -s none -S normal -b --list-cc=none -q > reportbug > > Can the interactiveness be avoided when the --template switch is used? > > The bug severity reflects the impact on another package rather than on > reportbug itself, so I'm not too sure about it. But it doesn't matter > because you'll fix this shortly anyway, right? ;-) > > Thanks! > > Peter > > -- Package-specific info: > ** Environment settings: > EMAIL="[EMAIL PROTECTED]" > DEBFULLNAME="Peter S Galbraith" > > -- System Information: > Debian Release: 3.1 > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: i386 (i686) > Kernel: Linux 2.4.27-1-k7 > Locale: LANG=C, LC_CTYPE=en_US.ISO-8859-1 (charmap=ISO-8859-1) > > Versions of packages reportbug depends on: > ii python2.3 2.3.3-1 An interactive high-level > object-o > > -- no debconf information > > > -- Chris Lawrence - http://blog.lordsutch.com/
