Your message dated Wed, 21 Sep 2011 15:07:11 -0400
with message-id <[email protected]>
and subject line close Bug#594177: reportbug crashes (with certain proxy 
environmental variables)
has caused the Debian Bug report #594177,
regarding Proxy error crashes 'reportbug', then 'reportbug' outputs a 
misleading error message.
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.)


-- 
594177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594177
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: reportbug
Version: 4.12.6
Severity: important


Simple 'reportbug <anything>' 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 report to Debian (per lsb_release).
    Querying Debian BTS for reports on reportbug (source)...
    Traceback (most recent call last):
      File "/usr/bin/reportbug", line 2098, in <module>
        main()
      File "/usr/bin/reportbug", line 1045, in main
        return iface.user_interface()
      File "/usr/bin/reportbug", line 1629, in user_interface
        version=pkgversion)
      File "/usr/lib/pymodules/python2.6/reportbug/ui/text_ui.py", line 552, in 
handle_bts_query
        for entry in hierarchy:
    TypeError: 'NoneType' object is not iterable

Real rough hack of a fix, before line 552 of 
"/usr/lib/pymodules/python2.6/reportbug/ui/text_ui.py"
add the lines:


        if hierarchy == None:
            hierarchy = []

That was enough to let me report this bug.


-- Package-specific info:
** Environment settings:
EDITOR="gedit"
VISUAL="gedit"
DEBEMAIL="[email protected]"
EMAIL="[email protected]"
DEBFULLNAME="Erik de Castro Lopo"

** /home/erikd/.reportbugrc:
mode expert

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=ANSI_X3.4-1968) 
(ignored: LC_ALL set to C)
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.6     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)
pn  emacs22-bin-common | <none>              (no description available)
ii  file                 5.04-5              Determines file type using "magic"
ii  gnupg                1.4.10-4            GNU privacy guard - a free PGP rep
ii  postfix [mail-transp 2.7.1-1             High-performance mail transport ag
ii  python-gtk2          2.17.0-4            Python bindings for the GTK+ widge
pn  python-gtkspell      <none>              (no description available)
pn  python-urwid         <none>              (no description available)
ii  python-vte           1:0.24.3-1          Python bindings for the VTE widget
ii  xdg-utils            1.0.2+cvs20100307-1 desktop integration utilities from

-- no debconf information



--- End Message ---
--- Begin Message ---
On Sat, 27 Aug 2011 11:45:16 +0200
Sandro Tosi <[email protected]> wrote:

> I just tried and I can't replicate this problem either with an empty
> http_proxy or an invalid value (non-existing proxy) not even with a
> valid one. Given we recently changed the way we fetch bug reports,
> could you please check with the latest version in sid and confirm it's
> gone/still happening?

Just tested with 'reportbug' v6.2.1, and it now works correctly, both
with or without an http_proxy.  Thanks maintainers!  Closing bug...


--- End Message ---

Reply via email to