Package: reportbug
Version: 4.4
Severity: normal

Hi,

reportbug blocks infinitely if it encounters unreadable directories
(files?) during package verification.
One example is the bugzilla3 (3.2.0.1-1) package which has some
directories in /usr/share with permissions 0750, owner root:www-data
(e.g. /usr/share/bugzilla3/lib) that I as normal user can't access and I
had to use the --no-verify option to report that as bug #533394.

Andreas


-- System Information:
Debian Release: squeeze/sid
  APT prefers stable
  APT policy: (800, 'stable'), (700, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages reportbug depends on:
ii  apt                           0.7.21     Advanced front-end for dpkg
ii  python                        2.5.4-2    An interactive high-level object-o
ii  python-reportbug              4.4        Python modules for interacting wit

reportbug recommends no packages.

Versions of packages reportbug suggests:
ii  debconf-utils                1.5.26      debconf utilities
ii  debsums                      2.0.44      verification of installed package 
pn  dlocate                      <none>      (no description available)
ii  file                         5.03-1      Determines file type using "magic"
ii  gnupg                        1.4.9-4     GNU privacy guard - a free PGP rep
ii  postfix [mail-transport-agen 2.5.5-1.1   High-performance mail transport ag
ii  python-gnome2-extras         2.19.1-3.1  Extra Python bindings for the GNOM
ii  python-gtk2                  2.12.1-6    Python bindings for the GTK+ widge
pn  python-urwid                 <none>      (no description available)
ii  python-vte                   1:0.16.14-4 Python bindings for the VTE widget

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to