Re: An email address for drive-by bug reports?

2023-04-09 Thread Sam Hartman
> "Ivan" == Ivan Shmakov writes: >> Having a bunch of problem reports that no one is interested in >> cluttering up package pages has a cost. Just for the same >> reasons you don't want these reports cluttering up your bugs from >> page, I perhaps don't want them cluttering

Re: An email address for drive-by bug reports?

2023-04-02 Thread Ivan Shmakov
> On 2023-03-23 05:30:01 +0100, Don Armstrong wrote: > On Fri, 17 Mar 2023, Ivan Shmakov wrote: >> It would’ve likely helped me if #1006801 were listed on >> http://bugs.debian.org/src:tinysshd . >> (I’m not entirely sure as to /why/ it got archived, TBH: it’s found in >> 20190101-1,

Re: An email address for drive-by bug reports?

2023-03-22 Thread Don Armstrong
On Fri, 17 Mar 2023, Ivan Shmakov wrote: > For an example, I’ve once spent hours trying to determine the cause of > a particular problem I was having. Turns out tinysshd(8) from Bullseye > has an interoperability issue with openssh-client from the same. It > would’ve likely helped me if #1006801

Re: An email address for drive-by bug reports?

2023-03-17 Thread Ivan Shmakov
> On 2023-03-01 16:30:01 +0100, Sam Hartman wrote: > Honestly, if there is not currently a submitter behind a bug---someone > who cares about it and is willing to look into requests for more > information or to help confirm a fix---I'm not particularly interested > in working on such a

Re: An email address for drive-by bug reports?

2023-03-07 Thread Paul Wise
On Mon, 2023-03-06 at 16:56 -0800, Don Armstrong wrote: > This is my viewpoint too, and why I don't plan on implementing or > accepting a patch to do nosubmitter unless someone can convince me > otherwise. The use-case presented in the thread seems reasonable to me; when you are submitting a bug

Re: An email address for drive-by bug reports?

2023-03-06 Thread Don Armstrong
On Wed, 01 Mar 2023, Sam Hartman wrote: > Honestly, if there is not currently a submitter behind a bug […] > that's often a sign the bug should be closed until someone comes along > who cares about the issue enough to interact with it. This is my viewpoint too, and why I don't plan on

Re: An email address for drive-by bug reports?

2023-03-01 Thread Gioele Barabucci
On 01/03/23 16:22, Sam Hartman wrote: Socially and culturally I do want to emphasize the idea that if you aren't willing (any more) to put energy behind your problem report, it's entirely fine if no one is going to put energy behind fixing it. That seems to me like a perfectly fine social

Re: An email address for drive-by bug reports?

2023-03-01 Thread Sam Hartman
> "Gioele" == Gioele Barabucci writes: Gioele> For example I have opened bugs years ago against packages Gioele> that I do not use anymore. These reports are still valid and Gioele> sometime others comment on them, but I would no longer be Gioele> able to, for example,

Re: An email address for drive-by bug reports?

2023-02-28 Thread Paul Wise
On Tue, 2023-02-28 at 18:36 +0100, Gioele Barabucci wrote: > Should there be a standard email address for "I'm reporting this because > I noticed it, but I'm not interested in it"-bug reports? Similar to the BTS noowner command, perhaps add a nosubmitter command? -- bye, pabs

An email address for drive-by bug reports?

2023-02-28 Thread Gioele Barabucci
Should there be a standard email address for "I'm reporting this because I noticed it, but I'm not interested in it"-bug reports? Orphaned packages get their maintainer address set to . Shouldn't something similar be available for bugs? For example I have opened bugs years ago against