Description of problem: Fedora32 provides maildir-utils 1.3.9 (1.20200229git17f38dc), which is a development release, and picked a very unlucky commit. The mu4e component (emacs mail client) of this very commit has the problem that replying to messages triggers an elisp backtrace, see: https://github.com/djcb/mu/issues/1536#issuecomment-605701728 Version-Release number of selected component (if applicable): 1.3.9 (1.20200229git17f38dc) How reproducible: Reply to a message Actual results: Elisp backtrace; see linked report. Expected results: Reply to a message Additional info: (note: I am the mu/mu4e maintainer and Fedora user, "mu" is the upstream name for "maildir utils") If Fedora really wants to ship a development version (rather than the released 1.2), I'd recommend picking the very latest (1.3.10, 70d1c05ecfc30 at this point), which has fixes for the above problem (and a bunch of others). I must stress that the current version is unusable (email client that errors out on replying to messages!), so hope this can be fixed for F32 still.
Right. I suppose that at this point it would make sense to go straight to 1.4.1. I chose this specific commit because it fixed the Guile bindings not getting built. But that was always a bit of a stopgap measure on my part. So now we can get back to using regular releases instead of development tags, I hope.
FEDORA-2020-70f0bc7a82 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-70f0bc7a82
FEDORA-2020-70f0bc7a82 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-70f0bc7a82` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-70f0bc7a82 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-70f0bc7a82 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.