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

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

Will my reportbug report be seen?

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

Contents

  Will my reportbug report be seen? Steve Dondley <s@dondley.com> - 2021-09-11 02:10 +0200
    Re: Will my reportbug report be seen? Steve Dondley <s@dondley.com> - 2021-09-11 02:20 +0200
      Re: Will my reportbug report be seen? Greg Wooledge <greg@wooledge.org> - 2021-09-11 02:20 +0200
        Re: Will my reportbug report be seen? Steve Dondley <s@dondley.com> - 2021-09-11 02:30 +0200
          Re: Will my reportbug report be seen? piorunz <piorunz@gmx.com> - 2021-09-11 03:20 +0200
        Re: Will my reportbug report be seen? Steve Dondley <s@dondley.com> - 2021-09-11 02:30 +0200
          Re: Will my reportbug report be seen? Brian <ad44@cityscape.co.uk> - 2021-09-11 12:30 +0200
            Re: Will my reportbug report be seen? Steve Dondley <s@dondley.com> - 2021-09-11 18:50 +0200
              Re: Will my reportbug report be seen? Brian <ad44@cityscape.co.uk> - 2021-09-11 19:00 +0200
                Re: Will my reportbug report be seen? Steve Dondley <s@dondley.com> - 2021-09-12 04:00 +0200
                Debian bug report closed or open? (was: Will my reportbug report be  seen?) l0f4r0@tuta.io - 2021-09-12 09:30 +0200
                  Re: Debian bug report closed or open? "Thomas Schmitt" <scdbackup@gmx.net> - 2021-09-12 10:10 +0200
                    Re: Debian bug report closed or open? l0f4r0@tuta.io - 2021-09-12 12:30 +0200
                      Re: Debian bug report closed or open? David <bouncingcats@gmail.com> - 2021-09-12 12:50 +0200
                        Re: Debian bug report closed or open? Brian <ad44@cityscape.co.uk> - 2021-09-12 13:50 +0200
                        Re: Debian bug report closed or open? l0f4r0@tuta.io - 2021-09-12 18:30 +0200
                          Re: Debian bug report closed or open? Brian <ad44@cityscape.co.uk> - 2021-09-12 19:20 +0200
          Re: Will my reportbug report be seen? Andrei POPESCU <andreimpopescu@gmail.com> - 2021-09-12 12:00 +0200

#239861 — Will my reportbug report be seen?

I used reportbug for the first time. The experience was a little 
confusing.

It appears to have gone through because I got an confirmation email:

Email subject:
1.4.11+dfsg.1-4: Please see issue at github: 
https://github.com/roundcube/roundcubemail/issues/8198

Email body:
============================================================
Package: 1.4.11+dfsg.1-4
Version: roundcube
Severity: normal

Dear Maintainer,

-- System Information:
Debian Release: 11.0
   APT prefers stable-security
   APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-cloud-amd64 (SMP w/2 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
==============================================================

So it looks like I mixed up the version and the package name. I don't 
know how I might correct this or if I need to. And the subject is a 
description of the bug, which seems weird.

Can I just leave this as is? Or can/should I correct it somehow?

[toc] | [next] | [standalone]

#239862

> Can I just leave this as is? Or can/should I correct it somehow?

Ok, while I was writing that last email, I got another confirmation:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994068

So I'm probably good?

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

#239863

On Fri, Sep 10, 2021 at 08:10:41PM -0400, Steve Dondley wrote:
> 
> > Can I just leave this as is? Or can/should I correct it somehow?
> 
> Ok, while I was writing that last email, I got another confirmation:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994068
> 
> So I'm probably good?

Someone will probably fix up the metadata.  But this is an extremely
poor bug report.  It has NO useful details at all.

You're basically relying on someone to go click on the URL you put
into the subject, read it, analyze it, figure out what it's talking
about, and then fix up your bug report to be readable.

This may happen in a timely manner, or it may not.  Your best bet at
this point is to wait a few days and see what happens.  If nobody
fixes it up before then, you might consider replying to the bug and
supplying an actual description of the bug.

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

#239864

> This may happen in a timely manner, or it may not.  Your best bet at
> this point is to wait a few days and see what happens.  If nobody
> fixes it up before then, you might consider replying to the bug and
> supplying an actual description of the bug.

OK, sounds like a plan. I see in the link I provided that there is a way 
to reply. I will wait a few days and give it a shot. Thanks!

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

#239870

On 11/09/2021 01:25, Steve Dondley wrote:
>
>> This may happen in a timely manner, or it may not.  Your best bet at
>> this point is to wait a few days and see what happens.  If nobody
>> fixes it up before then, you might consider replying to the bug and
>> supplying an actual description of the bug.
>
> OK, sounds like a plan. I see in the link I provided that there is a way
> to reply. I will wait a few days and give it a shot. Thanks!
>
Just reply to bug report and write full details now, instead of waiting.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀

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

#239865

On 2021-09-10 08:15 PM, Greg Wooledge wrote:
> On Fri, Sep 10, 2021 at 08:10:41PM -0400, Steve Dondley wrote:
>> 
>> > Can I just leave this as is? Or can/should I correct it somehow?
>> 
>> Ok, while I was writing that last email, I got another confirmation:
>> 
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994068
>> 
>> So I'm probably good?
> 
> Someone will probably fix up the metadata.  But this is an extremely
> poor bug report.  It has NO useful details at all.
> 
> You're basically relying on someone to go click on the URL you put
> into the subject, read it, analyze it, figure out what it's talking
> about, and then fix up your bug report to be readable.

Yeah, had I known my bug report would be thrown in the subject, I would 
have changed things up a bit.

The link that got thrown in the subject provides all the details, 
however.

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

#239875

On Fri 10 Sep 2021 at 20:22:43 -0400, Steve Dondley wrote:

> On 2021-09-10 08:15 PM, Greg Wooledge wrote:
> > On Fri, Sep 10, 2021 at 08:10:41PM -0400, Steve Dondley wrote:
> > > 
> > > > Can I just leave this as is? Or can/should I correct it somehow?
> > > 
> > > Ok, while I was writing that last email, I got another confirmation:
> > > 
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994068
> > > 
> > > So I'm probably good?
> > 
> > Someone will probably fix up the metadata.  But this is an extremely
> > poor bug report.  It has NO useful details at all.
> > 
> > You're basically relying on someone to go click on the URL you put
> > into the subject, read it, analyze it, figure out what it's talking
> > about, and then fix up your bug report to be readable.
> 
> Yeah, had I known my bug report would be thrown in the subject, I would have
> changed things up a bit.
> 
> The link that got thrown in the subject provides all the details, however.

The subject line should express as simply as possible what the issue
is. In your case it seems to involve stale files. URLs in the body of
the mail to *support* the report are OK. A URL that requires some
time to read needs thinking about including.

You could submit a new (revamped) report and close #994068. Why wait?

-- 
Brian.

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

#239877

On 2021-09-11 06:27 AM, Brian wrote:
> On Fri 10 Sep 2021 at 20:22:43 -0400, Steve Dondley wrote:
> 
>> On 2021-09-10 08:15 PM, Greg Wooledge wrote:
>> > On Fri, Sep 10, 2021 at 08:10:41PM -0400, Steve Dondley wrote:
>> > >
>> > > > Can I just leave this as is? Or can/should I correct it somehow?
>> > >
>> > > Ok, while I was writing that last email, I got another confirmation:
>> > >
>> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994068
>> > >
>> > > So I'm probably good?
>> >
>> > Someone will probably fix up the metadata.  But this is an extremely
>> > poor bug report.  It has NO useful details at all.
>> >
>> > You're basically relying on someone to go click on the URL you put
>> > into the subject, read it, analyze it, figure out what it's talking
>> > about, and then fix up your bug report to be readable.
>> 
>> Yeah, had I known my bug report would be thrown in the subject, I 
>> would have
>> changed things up a bit.
>> 
>> The link that got thrown in the subject provides all the details, 
>> however.
> 
> The subject line should express as simply as possible what the issue
> is. In your case it seems to involve stale files. URLs in the body of
> the mail to *support* the report are OK. A URL that requires some
> time to read needs thinking about including.
> 
> You could submit a new (revamped) report and close #994068. Why wait?

Not sure if I can close it or if maintainer needs to: 
https://www.debian.org/doc/manuals/debian-bugs/ch4.en.html

It doesn't state how the originator of the bug report can close it.

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

#239878

On Sat 11 Sep 2021 at 12:44:30 -0400, Steve Dondley wrote:

> On 2021-09-11 06:27 AM, Brian wrote:
> > On Fri 10 Sep 2021 at 20:22:43 -0400, Steve Dondley wrote:
> > 
> > > On 2021-09-10 08:15 PM, Greg Wooledge wrote:
> > > > On Fri, Sep 10, 2021 at 08:10:41PM -0400, Steve Dondley wrote:
> > > > >
> > > > > > Can I just leave this as is? Or can/should I correct it somehow?
> > > > >
> > > > > Ok, while I was writing that last email, I got another confirmation:
> > > > >
> > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994068
> > > > >
> > > > > So I'm probably good?
> > > >
> > > > Someone will probably fix up the metadata.  But this is an extremely
> > > > poor bug report.  It has NO useful details at all.
> > > >
> > > > You're basically relying on someone to go click on the URL you put
> > > > into the subject, read it, analyze it, figure out what it's talking
> > > > about, and then fix up your bug report to be readable.
> > > 
> > > Yeah, had I known my bug report would be thrown in the subject, I
> > > would have
> > > changed things up a bit.
> > > 
> > > The link that got thrown in the subject provides all the details,
> > > however.
> > 
> > The subject line should express as simply as possible what the issue
> > is. In your case it seems to involve stale files. URLs in the body of
> > the mail to *support* the report are OK. A URL that requires some
> > time to read needs thinking about including.
> > 
> > You could submit a new (revamped) report and close #994068. Why wait?
> 
> Not sure if I can close it or if maintainer needs to:
> https://www.debian.org/doc/manuals/debian-bugs/ch4.en.html

It's your submission; you can close it, In fact, any user can clos
 it.
 
> It doesn't state how the originator of the bug report can close it.

Send a mail to xxxxxx-done@bugs.debian.org. Give a reason for the
closure.

-- 
Brian.

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

#239890

>> It doesn't state how the originator of the bug report can close it.
> 
> Send a mail to xxxxxx-done@bugs.debian.org. Give a reason for the
> closure.

Got it. Thanks for the help.

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

#239899 — Debian bug report closed or open? (was: Will my reportbug report be seen?)

Hi,

11 sept. 2021, 18:52 de ad44@cityscape.co.uk:

> It's your submission; you can close it, In fact, any user can clos
>  it.
>
By the way, how can one see that a bug is closed and not open please?

For example, I know that the bug #958402 [1] has been closed because I received an email notification for that (I'm the submitter) but it's written nowhere in the webpage itself (at least I can't find it...).
[1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402

l0f4r0

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

#239905 — Re: Debian bug report closed or open?

Hi,

l0f4r0@tuta.io wrote:
> By the way, how can one see that a bug is closed and not open please?
> [1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402

I think you can recognize it by the "Done:" header on the web page:

  Done: Marc Haber <mh+debian-packages@zugschlus.de>

I see it in an old bug that was closed by a package release
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731023
but not in a still open bug which is awaiting closure by package release
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993646


(The release close mechanism can be seen in the debian/changelog
of the affected package:
  * Introduced debian/xorriso.info list. (Closes: #731023)
This way the maintainer does not have to remember solved bugs when the
fixed release gets out.)


Have a nice day :)

Thomas

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

#239912 — Re: Debian bug report closed or open?

Hi,

12 sept. 2021, 10:00 de scdbackup@gmx.net:

> l0f4r0@tuta.io wrote:
>
>> By the way, how can one see that a bug is closed and not open please?
>> [1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
>>
> I think you can recognize it by the "Done:" header on the web page:
>
>  Done: Marc Haber <> mh+debian-packages@zugschlus.de> >
>
Well spotted Thomas!

It makes sense indeed with the email address <nnn-done@bugs.debian.org> used to close a bug.

Thanks & have a great week-end!
l0f4r0

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

#239914 — Re: Debian bug report closed or open?

On Sun, 12 Sept 2021 at 20:20, <l0f4r0@tuta.io> wrote:
> 12 sept. 2021, 10:00 de scdbackup@gmx.net:
> > l0f4r0@tuta.io wrote:
> >
> >> By the way, how can one see that a bug is closed and not open please?
> >> [1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
> >>
> > I think you can recognize it by the "Done:" header on the web page:
> >
> >  Done: Marc Haber <> mh+debian-packages@zugschlus.de> >

Also, as an additional confirmation ...
On the above bug page:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
the second link is the package name "sudo", which goes to
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo
where under the heading
  "Resolved bugs -- Normal bugs"
the bug number 958402 is shown with a strikethrough font
(ie it has a horizontal line through the digits).

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

#239920 — Re: Debian bug report closed or open?

On Sun 12 Sep 2021 at 20:45:13 +1000, David wrote:

> On Sun, 12 Sept 2021 at 20:20, <l0f4r0@tuta.io> wrote:
> > 12 sept. 2021, 10:00 de scdbackup@gmx.net:
> > > l0f4r0@tuta.io wrote:
> > >
> > >> By the way, how can one see that a bug is closed and not open please?
> > >> [1] : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
> > >>
> > > I think you can recognize it by the "Done:" header on the web page:
> > >
> > >  Done: Marc Haber <> mh+debian-packages@zugschlus.de> >
> 
> Also, as an additional confirmation ...
> On the above bug page:
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
> the second link is the package name "sudo", which goes to
>   https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo
> where under the heading
>   "Resolved bugs -- Normal bugs"
> the bug number 958402 is shown with a strikethrough font
> (ie it has a horizontal line through the digits).

A good tip. However, a point to bear in mind is that Resolved bugs are
only visible for a few months (3?, 6?) after being closed.

-- 
Brian.

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

#239929 — Re: Debian bug report closed or open?

Hi,

12 sept. 2021, 12:45 de bouncingcats@gmail.com:

> Also, as an additional confirmation ...
> On the above bug page:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
> the second link is the package name "sudo", which goes to
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo
> where under the heading
> "Resolved bugs -- Normal bugs"
> the bug number 958402 is shown with a strikethrough font
> (ie it has a horizontal line through the digits).
>
Yes, thank you David.

12 sept. 2021, 13:42 de ad44@cityscape.co.uk:

> A good tip. However, a point to bear in mind is that Resolved bugs are
> only visible for a few months (3?, 6?) after being closed.
>
Actually, it appears they get archived after some time.

You can access them by appending "&archive=yes" to the URL of the package on the BTS.

For example regarding sudo package:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo&archive=yes
Best regards,
l0f4r0

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

#239931 — Re: Debian bug report closed or open?

On Sun 12 Sep 2021 at 18:26:57 +0200, l0f4r0@tuta.io wrote:

> Hi,
> 
> 12 sept. 2021, 12:45 de bouncingcats@gmail.com:
> 
> > Also, as an additional confirmation ...
> > On the above bug page:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958402
> > the second link is the package name "sudo", which goes to
> > https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo
> > where under the heading
> > "Resolved bugs -- Normal bugs"
> > the bug number 958402 is shown with a strikethrough font
> > (ie it has a horizontal line through the digits).
> >
> Yes, thank you David.
> 
> 12 sept. 2021, 13:42 de ad44@cityscape.co.uk:
> 
> > A good tip. However, a point to bear in mind is that Resolved bugs are
> > only visible for a few months (3?, 6?) after being closed.
> >
> Actually, it appears they get archived after some time.
> 
> You can access them by appending "&archive=yes" to the URL of the package on the BTS.
> 
> For example regarding sudo package:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=sudo&archive=yes

Tha's another excellent tip!

-- 
Brian.

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

#239908

[Multipart message — attachments visible in raw view] — view raw

On Vi, 10 sep 21, 20:22:43, Steve Dondley wrote:
> 
> Yeah, had I known my bug report would be thrown in the subject, I would have
> changed things up a bit.

The report should still go in the message body, the subject (and bug 
title) is supposed to represent a concise summary.

For reference, the text in reportbug is:

    Briefly describe the problem (max. 100 characters allowed). This 
    will be the bug email subject, so keep the summary as concise as 
    possible, for example: "fails to send email" or "does not start with 
    -q option specified" (enter Ctrl+c to exit reportbug without 
    reporting a bug).


How would you reword it to make it clearer?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [standalone]

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

csiph-web