http://bugzilla.suse.com/show_bug.cgi?id=1094717 http://bugzilla.suse.com/show_bug.cgi?id=1094717#c5 --- Comment #5 from David Sterba --- (In reply to Dr. Werner Fink from comment #2)

Hmm ... mutt here had already been patched a long time ago, that is mutt was never the original mutt as there was always (bug) reports and feature requests to add those patches. Now as the NeoMutt project had maintained and integrated those patches and released in past a patch set and now their own version of mutt called neomutt, the mutt here is in fact a neomutt.

No it's not, closest match is that opensuse-mutt has some old snapshot of neomutt sources, that's now half a year old. Possibly fixing some of the bugs you refer to, but otherwise it's just another 3rd party patch to mutt. The neomutt project moves forward, has replaced the build system and adds new features so updating the neomutt patch inside opensuse-mutt would not make much sense.

Let's gues what happens if I switch to original mutt back, that is without any patches: I'll see a lot of bug reports that features do not work anymore.

That's the result of unfortuante state of mutt upstream that essentially forced every distro to track several fixes on their own. And not only that, also features, like sidebar, so this becomes impossible to revert to upstream-mutt because everybody is now used to the patched mutt.

A solution would be to rename current mutt to neomutt and add a new package mutt. But for the last one an other maintainer/bugowner is required.

The solution is to push all opensuse-specific patches to upstream mutt or drop them from the package. Neomutt is now a different project and what is inside the opensuse-mutt does not reflect the current state so renaming would cause yet more confusion we did not have in the first place. -- You are receiving this mail because: You are on the CC list for the bug.