Done.
Mike Frysinger wrote:
> Glenn Morris wrote:
> > I see autoconf uses savannah for bug reports.
> > So long as simply sending a mail to bug-autoconf doesn't open a savannah
> > issue,
> > I can set the autoconf maintainer to bug-autoconf, so that mails go to
> > the right place. (It tends not to
On 08 Feb 2022 22:11, Glenn Morris wrote:
> Mike Frysinger wrote:
> > what can we do to suppress the notifications ? can we set the
> > maintainer address to /dev/null for a few known packages like autoconf
> > & libtool ?
>
> I'm not sure if /dev/null works. But I think it would be better to
>
Mike Frysinger wrote:
> what can we do to suppress the notifications ? can we set the
> maintainer address to /dev/null for a few known packages like autoconf
> & libtool ?
I'm not sure if /dev/null works. But I think it would be better to
simply close the issue, ideally with instructions on
On 08 Feb 2022 11:03, Glenn Morris wrote:
> I see this bug, and a few others, were reassigned to autoconf.
> autoconf does not use debbugs to track bugs, so the autoconf package has
> no maintainer address
i'm aware of this. Zach was debating migrating, but until then, seemed
better to park it
I see this bug, and a few others, were reassigned to autoconf.
autoconf does not use debbugs to track bugs, so the autoconf package has
no maintainer address, causing mails to end up on the help-debbugs list.
https://debbugs.gnu.org/cgi/pkgreport.cgi?pkg=autoconf
Ref eg
On 30 Jan 2015 17:49, Pavel Raiskup wrote:
> [+cc autoconf as this should be done in cooperation]
>
> On Thursday 08 of January 2015 16:43:02 Pavel Raiskup wrote:
> > Hi, automake-1.15 behaves differently when AC_CONFIG_AUX_DIR is specified
> > after AC_USE_SYSTEM_EXTENSIONS (example attached
[+cc autoconf as this should be done in cooperation]
On Thursday 08 of January 2015 16:43:02 Pavel Raiskup wrote:
Hi, automake-1.15 behaves differently when AC_CONFIG_AUX_DIR is specified
after AC_USE_SYSTEM_EXTENSIONS (example attached which worked with
automake-1.14.1):
$ autoreconf -vfi
