[Reportbug-maint] Bug#345520: Re : reportbug: should keep output of debconf-show
chaica
chaica at ohmytux.com
Mon Jun 15 17:40:33 UTC 2009
tags 345520 unreproducible
tags 345520 moreinfo
thanks
Hi Wladimir,
Could you confirm the bug has been solved by newer releases of
reportbug ? I'm unable to reproduce it with newest releases.
Bye,
Carl Chenet
> debconf had split up its config DBs and now have "passwords.dat"
> readable only for root. So when reportbug is run by ordinary user,
> debconf-show exits with non-zero status, and reportbug writes in
> report text that it has failed. While debconf-show just writes a
> warning, and then outputs all meaningful info it could read as current
> user. I think reportbug should always add stdout and stderr output of
> debconf-show to the report, and inform about numeric non-zero exit code,
> not just write "debconf-show failed".
>
> -- Package-specific info:
> ** /home/mwg/.reportbugrc:
> mode standard
>
> -- System Information:
> Debian Release: testing/unstable
> APT prefers breezy
> APT policy: (500, 'breezy'), (500, 'unstable'), (500, 'stable')
> Architecture: i386 (i686)
> Shell: /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.14
> Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8)
>
> Versions of packages reportbug depends on:
> ii python2.3 2.3.5-9 An interactive high-level object-o
>
> Versions of packages reportbug recommends:
> pn python2.3-cjkcodecs | python2 <none> (no description available)
>
> -- debconf-show failed
>
More information about the Reportbug-maint
mailing list