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: mutt and neomutt In stretch, the package mutt had patches applied from the sources at https://www.neomutt.org;>https://www.neomutt.org. Starting from buster, the package providing /usr/bin/mutt will instead be purely based on the original sources from https://www.mutt.org;>https://www.mutt.org, and a separate neomutt package is available providing /usr/bin/neomutt. This means that some of the features that were previously provided by mutt are no longer available. If this breaks your configuration you can install neomutt instead. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Bug#928353: Fwd: release-notes: document mutt vs neomutt in buster
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.
Bug#928353: Fwd: release-notes: document mutt vs neomutt in buster
Thanks for pinging me, I missed this, let me comment on the bug. On Sun, May 05, 2019 at 02:51:35PM +0200, Paul Gevers wrote: > 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 > To: Debian Bug Tracking System > > Package: release-notes > X-Debbugs-CC: m...@packages.debian.org, j...@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/ > > >
Bug#928353: Fwd: release-notes: document mutt vs neomutt in buster
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 To: Debian Bug Tracking System Package: release-notes X-Debbugs-CC: m...@packages.debian.org, j...@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/ signature.asc Description: OpenPGP digital signature
