Hello,
On Fri, Jan 7, 2011 at 08:08, A. Costa wrote:
> As an experiment, from the shell I unset my 'ftp_proxy=' and
> 'http_proxy=' environmental variables. After which 'reportbug' worked
> as expected. IIRC 'reportbug' wasn't formerly sensitive to
> proxy environmental variables. (My system's
reopen 594177 !
retitle 594177 Proxy error crashes 'reportbug', then 'reportbug' outputs a
misleading error message.
thanks
For full explanation, please see my previous post:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594177#40
(Jiffy summary: the crash happens when proxy s
reopen 594177 !
thanks
A week back E. de Castro Lopo speculated that the errors for bug
#594177 seemed related to BTS availability. Maintainer Tosi was unable
to reproduce the bug, and promptly closed it.
Comments, speculation, and a probable cause (might be reproducible, see
end) follow...
Sandro Tosi wrote:
> do you still see this bug?
No I don't. I think this was only a problem when the BTS itself
was down or have some sort of a problem.
Cheers,
Erik
--
--
Erik de Castro Lopo
http://www.mega-nerd.com/
--
To
Hi Erik
On Tue, Aug 24, 2010 at 12:44, Erik de Castro Lopo wrote:
> Package: reportbug
> Version: 4.12.6
> Severity: important
>
>
> Simple 'reportbug ' results in:
>
> Getting status for reportbug...
> Verifying package integrity...
> Checking for newer versions at packages.debian.org,
Package: reportbug
Version: 4.12.6
Severity: important
Simple 'reportbug ' results in:
Getting status for reportbug...
Verifying package integrity...
Checking for newer versions at packages.debian.org, incoming.debian.org and
http://ftp-master.debian.org/new.html
Will send repor
6 matches
Mail list logo
