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-d...@bugs.debian.org. Give a reason for the closure. -- Brian.
