Your message dated Wed, 4 Aug 2010 21:13:00 +0200
with message-id <[email protected]>
and subject line Re: Bug#591686: Long bug lists (like linux-2.6) make reportbug
think BTS won't respond
has caused the Debian Bug report #591686,
regarding Long bug lists (like linux-2.6) make reportbug think BTS won't respond
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
591686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591686
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 4.12.4
Severity: normal
When reporting a bug on a package that has a very long bug list, like
linux-2.6, I get this:
Querying Debian BTS for reports on linux-2.6 (source)...
Unable to connect to Debian BTS; continue [y|N|?]?
This doesn't happen for packages with smaller bug lists. Visiting
http://bugs.debian.org/linux-2.6 in a web browser also takes a long time
to load, but it does eventually load.
- Josh Triplett
-- Package-specific info:
** Environment settings:
EDITOR="/home/josh/.local/bin/vim-wrapper"
DEBEMAIL="[email protected]"
EMAIL="[email protected]"
DEBFULLNAME="Josh Triplett"
NAME="Josh Triplett"
INTERFACE="text"
** /home/josh/.reportbugrc:
reportbug_version "3.21.2"
mode advanced
ui text
no-cc
header "X-Debbugs-CC: [email protected]"
smtphost reportbug.debian.org:587
header "X-Debbugs-No-Ack: ack!"
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.35-rc6-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages reportbug depends on:
ii apt 0.7.25.3 Advanced front-end for dpkg
ii python 2.6.5-11 interactive high-level object-orie
ii python-reportbug 4.12.4 Python modules for interacting wit
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn debconf-utils <none> (no description available)
ii debsums 2.0.48+nmu1 tool for verification of installed
pn dlocate <none> (no description available)
ii emacs23-bin-common 23.2+1-2 The GNU Emacs editor's shared, arc
ii file 5.04-4 Determines file type using "magic"
ii gnupg 1.4.10-4 GNU privacy guard - a free PGP rep
pn postfix | exim4 | ma <none> (no description available)
ii python-gtk2 2.17.0-3 Python bindings for the GTK+ widge
pn python-gtkspell <none> (no description available)
pn python-urwid <none> (no description available)
pn python-vte <none> (no description available)
ii xdg-utils 1.0.2+cvs20100307-1 desktop integration utilities from
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello Josh,
On Wed, Aug 4, 2010 at 20:56, Josh Triplett <[email protected]> wrote:
> Package: reportbug
> Version: 4.12.4
> Severity: normal
>
> When reporting a bug on a package that has a very long bug list, like
> linux-2.6, I get this:
>
> Querying Debian BTS for reports on linux-2.6 (source)...
> Unable to connect to Debian BTS; continue [y|N|?]?
>
> This doesn't happen for packages with smaller bug lists. Visiting
> http://bugs.debian.org/linux-2.6 in a web browser also takes a long time
> to load, but it does eventually load.
Here it's what's written in /usr/share/doc/reportbug/README.Users.gz :
Network Errors and Timeout
==========================
There are situations where a network error is returned, for example:
"Unable to connect to BTS". These of course can be caused by a network
unavailability.
Another explanation can be that the remote resource is so slow to
respond (or it's stale) and a timeout is triggered. By default this
timeout is set to 1 minute; so in case of such an error, if you're
unsure that it's a clear network outage, you can try to pass
`--timeout <secs>' to either `reportbug' or `querybts' and see if it
solves the issue.
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
