Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #176910 > unrolled thread

Multiple reportbug failure reports

Started byCindy-Sue Causey <butterflybytes@gmail.com>
First post2017-01-22 20:40 +0100
Last post2017-01-23 06:20 +0100
Articles 4 — 4 participants

Back to article view | Back to linux.debian.user


Contents

  Multiple reportbug failure reports Cindy-Sue Causey <butterflybytes@gmail.com> - 2017-01-22 20:40 +0100
    Re: Multiple reportbug failure reports Gary Roach <gary719_list1@verizon.net> - 2017-01-22 20:50 +0100
      Re: Multiple reportbug failure reports Mark Fletcher <mark27q1@gmail.com> - 2017-01-23 00:00 +0100
    Re: Multiple reportbug failure reports kamaraju kusumanchi <raju.mailinglists@gmail.com> - 2017-01-23 06:20 +0100

#176910 — Multiple reportbug failure reports

FromCindy-Sue Causey <butterflybytes@gmail.com>
Date2017-01-22 20:40 +0100
SubjectMultiple reportbug failure reports
Message-ID<t2w9A-4NB-3@gated-at.bofh.it>
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
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

[toc] | [next] | [standalone]


#176911

FromGary Roach <gary719_list1@verizon.net>
Date2017-01-22 20:50 +0100
Message-ID<t2wjg-4QZ-3@gated-at.bofh.it>
In reply to#176910
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.

[toc] | [prev] | [next] | [standalone]


#176914

FromMark Fletcher <mark27q1@gmail.com>
Date2017-01-23 00:00 +0100
Message-ID<t2zh8-6JM-7@gated-at.bofh.it>
In reply to#176911
On Sun, Jan 22, 2017 at 11:47:39AM -0800, Gary Roach wrote:
> On 01/22/2017 11:32 AM, Cindy-Sue Causey wrote:
> 
> 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.
> 
I am sure I remember seeing on this distribution list recently a fair 
number of reports that reportbug in >Jessie is currently broken...

(I thankfully have not had occasion to use it recently, but as I 
understand it reportbug in Jessie is OK)

The issue seems to be known and hopefully someone is working on it...

Mark

[toc] | [prev] | [next] | [standalone]


#176923

Fromkamaraju kusumanchi <raju.mailinglists@gmail.com>
Date2017-01-23 06:20 +0100
Message-ID<t2FcS-2eh-15@gated-at.bofh.it>
In reply to#176910
On Sun, Jan 22, 2017 at 2:32 PM, Cindy-Sue Causey
<butterflybytes@gmail.com> wrote:
> 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. :)

Reportbug is just a tool that makes it "easy" to report a bug. It is a
very useful tool but by no means the only option to report bugs. For
example,  you can report bugs by sending an e-mail to
submit@bugs.debian.org with a special format. See
https://www.debian.org/Bugs/Reporting for more details.

-- 
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web