>>>>> Chris Hofstaedtler <z...@debian.org> wrote:
> Subject: no additional feedback
> Closing for lack of anything actionable.
JFTR, the workaround for this issue is to put -e either to the
command line, or to the MORE environment variable’s value.
It seems like in Bullseye, more(1) ignores unrecognized options,
so that should work for ~/.profile (or any other file used to
initialize user’s environment) shared across Debian releases.
I believe that the correct course of action is not to close the
report, as the problem still exists, is still reproducible, and
still affects, or can affect, Debian users; but rather to downgrade
to wishlist and tag as wontfix.
At the very least, that would help avoid duplicate reports of this
same issue. (As to actionability, I understand the unwillingness
to deviate from upstream, but I’d argue that such a deviation /is/
nevertheless an ‘action’ that /can/ be performed by a maintainer.)
My understanding is that the Debian BTS exists for the benefit
of Debian users at large, not just the developers and maintainers;
and in particular serves to inform the users of the issues they
can run into upon upgrade. (And if that’s somehow not the case,
I’d kindly suggest that an alternative BTS is created for that
purpose.)
TYC.
--
FSF associate member #7257 http://am-1.org/~ivan/
