Adrian Bunk writes:
> I am sometimes getting an email from the BTS that this "typo in the
> manpage" bug I reported 20 years ago has just been fixed in the "New
> maintainer" upload of a package.
> When working on orphaned packages or doing NMUs, it is also often useful
> for me to see the
On Mon, Feb 13, 2023 at 08:05:50AM -0800, Russ Allbery wrote:
>...
> So in short I agree with Holger: it really depends. It's rude to ask
> someone to do a bunch of work when you have no intention of following
> through on that work, which happens a lot when new volunteers do bug
> triage without
Adrian Bunk writes:
> I remember being pretty pissed when in a different open source project
> some abuser asked me every 6-12 months whether I can still reproduce the
> problem with the latest upstream version, each time I spent several
> hours for confirming it, but this abuser never bothered
On Mon, Feb 13, 2023 at 10:33:51AM +, Holger Levsen wrote:
> On Sat, Feb 11, 2023 at 10:45:16PM +0200, Adrian Bunk wrote:
> > On Mon, Feb 06, 2023 at 10:07:59AM -0700, Sam Hartman wrote:
> > > Most of us do not prefer to close bugs simply because they are old.
> > It creates angry users and no
On Sat, Feb 11, 2023 at 10:45:16PM +0200, Adrian Bunk wrote:
> On Mon, Feb 06, 2023 at 10:07:59AM -0700, Sam Hartman wrote:
> > Most of us do not prefer to close bugs simply because they are old.
> It creates angry users and no real benefits.
this is undoubtingly true for some bugs and users.
On Mon, Feb 06, 2023 at 10:07:59AM -0700, Sam Hartman wrote:
>...
> Most of us do not prefer to close bugs simply because they are old.
It creates angry users and no real benefits.
> But closing bugs with a moreinfo tag when information has not been
> provided in six months to a year is likely
On Mon, 2023-02-06 at 10:07 -0700, Sam Hartman wrote:
> It's even appropriate to ask if the bug still happens.
I'd like to see people asking that to put a slight amount of effort
into reproducing the bug, especially if there are documented or obvious
steps towards that. I recently encountered a
> "Tomas" == Tomas Pospisek writes:
Tomas> All that said, I have never received negative feedback to
Tomas> these bug triages that I am occassionaly doing and am under
Tomas> the impression that the maintainers *do* appreciate someone
Tomas> going over their packages bugs
On 06.02.23 11:51, Santiago Vila wrote:
El 6/2/23 a las 11:26, Brian Thompson escribió:
I understand that the usual way to close out bug reports is having the
original author do it themselves. What's the policy on closing bug
reports
that haven't had activity in over 6 months?
Let the
On Mon, 2023-02-06 at 11:51 +0100, Santiago Vila wrote:
> Let the maintainers handle their bugs.
> Old bugs should not be closed just because they are "old".
>
> For example, I have an open bug which is 26 years old:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=5898
>
> and I don't see
El 6/2/23 a las 11:26, Brian Thompson escribió:
I understand that the usual way to close out bug reports is having the
original author do it themselves. What's the policy on closing bug reports
that haven't had activity in over 6 months?
Let the maintainers handle their bugs.
Old bugs should
I understand that the usual way to close out bug reports is having the
original author do it themselves. What's the policy on closing bug reports
that haven't had activity in over 6 months?
Specifically I am talking about the following:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007922
12 matches
Mail list logo
