Re: Multiple reportbug failure reports

[Gary Roach <gary719_list1@verizon.net>]

On 01/22/2017 11:32 AM, Cindy-Sue Causey wrote:
> Hi.. This is just an observation. I already had 3 half finished drafts
> to three different threads when a fourth instance of reportbug failure
> just popped up, as well. Here they are in no particular order:
>
> 1) Re: reportbug and remapped "edit"; 2017.01.12 (consensus of two
> individuals momentarily pondering whether thread's subject matter
> caused reportbug failure)
> https://lists.debian.org/debian-user/2017/01/msg00454.html
>
> 2) Dependency problem with virtualbox-guest-x11; 2017.01.10 (reportbug
> crashing unrelated to thread's subject matter)
> https://lists.debian.org/debian-user/2017/01/msg00377.html
>
> 3) Re: Re: iio-sensor-proxy fills my syslog on debian testing;
> 2017.01.22 (reportbug crashing unrelated to thread's subject matter)
> https://lists.debian.org/debian-user/2017/01/msg00751.html
>
> 4) Errors were encountered while processing python3.5 etc; 2017.01.21
> (OP suspects python3.5* upgrade killed reportbug, but maybe not k/t
> the three other instances above?)
> https://lists.debian.org/debian-user/2017/01/msg00723.html
>
> A critical malfunction of the otherwise ever increasingly user
> friendly reportbug is a huge, nasty disruption in the forward motion
> of successful Debian maintenance and releases. The catch-22 is that
> Debian users need... reportbug... to report an apparent bug with....
> reportbug. :)
>
> Just lurking out loud... :)
>
> Cindy
Hi Cindy

Thanks for the compilation. Tho Python3.5 complaint is mine. Since 
reportbug is a python package, I will bet that python is the problem. I 
have filed a bug report by email. I t is #852163. I traced the problem 
back to the python3.5-minimal package. Hopefully the fix will come soon. 
It is obvious that this problem is causing all kinds of glitches. Is it 
all with stretch users or all versions I wonder. I've been doing some 
development work with python of late and have had my desktop freeze up 
periodically. I thought it was my development environment. Now I think 
it all may be due to the python problem.

Regards

Gary R.