Bug#928353: Fwd: release-notes: document mutt vs neomutt in buster
Antonio Radici wrote:
> This is what I propose to write down in the release notes, feel free to adjust
> as you see fit
Thanks!
>
> ====
> Starting from Buster, the mutt package will be shipped again from the original
> sources from https://www.mutt.org, this means that some of the features that
> were previously available due to patches applied to the mutt project, which we
> shipped as 'mutt' for the Stretch release, are no longer availables and that
> your configuration might be broken.
>
> If you want to restore the previous behavior you can install the 'neomutt'
> package which will ship the '/usr/bin/neomutt' binary; that is built off the
> sources from https://www.neomutt.org.
This describes things in an odd order. Could we explain the Stretch
situation first, *then* what's happening in Buster? And that
explanation needs to include the fact that the source of the patches
applied to the Debian mutt package was neomutt. Something like:
<section id="mutt and neomutt">
<!-- stretch to buster -->
<title>mutt and neomutt</title>
<para>
In stretch, the package <systemitem type="package">mutt</systemitem>
had patches applied from the sources at <ulink
url="https://www.neomutt.org">https://www.neomutt.org</ulink>. Starting
from buster, the package providing <literal>/usr/bin/mutt</literal> will
instead be purely based on the original sources from <ulink
url="https://www.mutt.org">https://www.mutt.org</ulink>, and a separate
<systemitem type="package">neomutt</systemitem> package is available
providing <literal>/usr/bin/neomutt</literal>.
</para>
<para>
This means that some of the features that were previously provided by
<systemitem type="package">mutt</systemitem> are no longer available. If
this breaks your configuration you can install <systemitem
type="package">neomutt</systemitem> instead.
</para>
</section>
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
Reply to: