-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Subject: reportbug: bails out with no message if dns resolving fails
Package: reportbug
Version: 3.30
Severity: normal

Hello,

I got this "wonderful" behaviour from reportbug while trying to report
a bug from a chroot of a freshly installed Etch system (from CD) which
didn't had networking configured.

- ----------8<-----------------

[EMAIL PROTECTED]:~$ reportbug reportbug
Warning: no reportbug configuration found.  Proceeding in novice mode.
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'Eddy Petrisor <[EMAIL PROTECTED]>' as your from address.
Getting status for reportbug...
Checking for newer versions at packages.debian.org...
Querying Debian BTS for reports on reportbug (source)...
[EMAIL PROTECTED]:~$ ping packages.debian.org
ping: unknown host packages.debian.org

- ----------8<-----------------


AFAICT, the rason is the lack of name resolving since the interface is
now up.

It would be nice if reportbug would at least display a message or, even
better, go automatically in offline mode (and announce) if resolving
fails.



- -- Package-specific info:

- -- System Information:
Debian Release: 4.0
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-powerpc
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8)

Versions of packages reportbug depends on:
ii  python                        2.4.3-11   An interactive high-level object-o
ii  python-central                0.5.8      register and build utility for Pyt

Versions of packages reportbug recommends:
pn  python-cjkcodecs | python-ico <none>     (no description available)

- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFXJaMY8Chqv3NRNoRAtK2AJ9kOjIsgywKz1fq9QvW9pTxATrIpgCeJh52
VlHsFAG1rP2pqIXlAgzWFh0=
=oGSu
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to