Bug#928353: release-notes: document mutt vs neomutt in buster

[Paul Gevers]

Package: release-notes
X-Debbugs-CC: ***@packages.debian.org, ***@debian.org

Dear (neo|)mutt maintainers,

I recently learned about the mutt versus neomutt situation in buster via
the blog [1] of jmtd (in X-D-CC). I believe mutt and neomutt warrant a
note in the release notes, don't you agree?

As the maintainers of this software, you are in the best position to
write this. Are you willing and able to provide a piece of text? MR
against the release notes archive [2] are welcome, but otherwise just
sent to this bug is fine.

Paul

[1] https://jmtd.net/log/mutt_year_zero/
[2] https://salsa.debian.org/ddp-team/release-notes/

[Paul Gevers]

Hi,

I'm not sure if this release-notes bug that I addressed to you actually
reached you.

Paul


-------- Forwarded Message --------
Subject: Bug#928353: release-notes: document mutt vs neomutt in buster
Date: Thu, 2 May 2019 18:53:55 +0200
From: Paul Gevers <***@debian.org>
To: Debian Bug Tracking System <***@bugs.debian.org>

Package: release-notes
X-Debbugs-CC: ***@packages.debian.org, ***@debian.org

Dear (neo|)mutt maintainers,

I recently learned about the mutt versus neomutt situation in buster via
the blog [1] of jmtd (in X-D-CC). I believe mutt and neomutt warrant a
note in the release notes, don't you agree?

As the maintainers of this software, you are in the best position to
write this. Are you willing and able to provide a piece of text? MR
against the release notes archive [2] are welcome, but otherwise just
sent to this bug is fine.

Paul

[1] https://jmtd.net/log/mutt_year_zero/
[2] https://salsa.debian.org/ddp-team/release-notes/

[Antonio Radici]

Thanks for pinging me, I missed this, let me comment on the bug.

Post by Paul Gevers
Hi,
I'm not sure if this release-notes bug that I addressed to you actually
reached you.
Paul
-------- Forwarded Message --------
Subject: Bug#928353: release-notes: document mutt vs neomutt in buster
Date: Thu, 2 May 2019 18:53:55 +0200
Package: release-notes
Dear (neo|)mutt maintainers,
I recently learned about the mutt versus neomutt situation in buster via
the blog [1] of jmtd (in X-D-CC). I believe mutt and neomutt warrant a
note in the release notes, don't you agree?
As the maintainers of this software, you are in the best position to
write this. Are you willing and able to provide a piece of text? MR
against the release notes archive [2] are welcome, but otherwise just
sent to this bug is fine.
Paul
[1] https://jmtd.net/log/mutt_year_zero/
[2] https://salsa.debian.org/ddp-team/release-notes/

[Antonio Radici]

This is what I propose to write down in the release notes, feel free to adjust
as you see fit

====
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.
====

[Justin B Rye]

Post by Antonio Radici
This is what I propose to write down in the release notes, feel free to adjust
as you see fit

Thanks!

Post by Antonio Radici
====
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>

[Debian Bug Tracking System]

Your message dated Tue, 7 May 2019 21:24:35 +0200
with message-id <40b73f4a-6821-ebf6-4261-***@debian.org>
and subject line Re: Bug#928353: Fwd: release-notes: document mutt vs neomutt in buster
has caused the Debian Bug report #928353,
regarding release-notes: document mutt vs neomutt in buster
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)