Sounds like a good strategy to me... I don't see a fix for this one
being accepted to stable-proposed-updates.


Chris

On 7/7/05, EspeonEefi <[EMAIL PROTECTED]> wrote:
> Package: reportbug
> Version: 3.8
> Followup-For: Bug #316608
> 
> This is a dup of #297452, but since the fix did not make it into sarge
> and this bug can be rather disconcerting, I think it's appropriate to
> tag it sarge and leave it open in the BTS.
> 
> Note that according to the logs of #297452, another way to remedy the
> situation is to uncomment the line "smtphost localhost"
> in /etc/reportbug.conf or ~/.reportbugrc. Of course, this requires
> having something appropriate listening on localhost:25.
> 
> -- Package-specific info:
> ** /home/espeoneefi/.reportbugrc:
> reportbug_version "3.8"
> mode expert
> ui text
> realname "EspeonEefi"
> email "[EMAIL PROTECTED]"
> 
> -- System Information:
> Debian Release: 3.1
> Architecture: i386 (i686)
> Kernel: Linux 2.6.8-2-686
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> 
> Versions of packages reportbug depends on:
> ii  python2.3                     2.3.5-3    An interactive high-level 
> object-o
> 
> -- no debconf information
-- 
Chris Lawrence - http://blog.lordsutch.com/

Reply via email to