GNU bug report logs - #61882
emacs-next-pgtk does not find emacs-org-roam, other path issues

Previous Next

Full log

Message #40 received at 61882-done <at> debbugs.gnu.org (full text, mbox):

From: Csepp <raingloom <at> riseup.net>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 61882-done <at> debbugs.gnu.org, Csepp <raingloom <at> riseup.net>
Subject: Re: bug#61882: emacs-next-pgtk does not find emacs-org-roam, other
 path issues
Date: Wed, 11 Oct 2023 00:52:51 +0200

Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:

> Hi,
>
> Csepp <raingloom <at> riseup.net> writes:
>
>> Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:
>>
>>> tags 61882 +notabug
>>> quit
>>
>> I don't think notabug applies until we actually know the root cause.
>
> Sadly I don't think there's anything actionable here until you can
> reproduce the problem and share the recipe with us, so I wanted to close
> the issue without it being marked as "resolved".

Neither "resolved" nor "notabug" are applicable.  If stalled incident
reports / issues are a problem, they should probably be marked as
stalled, or needinfo, for easy filtering.  Marking it as notabug is just
going to make the job of the next person harder when they search for
issues related to these symptoms.

I appreciate all the work going into closing old issues, but I don't
think chasing a low open issue count should be a goal unto itself
See https://fvsch.com/stale-bots .

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.