Please follow the unresponsive maintainer policy:

https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers

I don't see where any of that was attempted. If you have, please point us to it.

In mentioned ticket maintainer so far not replied.
In other ticket https://bugzilla.redhat.com/show_bug.cgi?id=1442842 in which I've submitted patch found issue maintainer is not replying as well within at least 3 weeks.
Maintainer did not scheduled any off time as well.
I'm not sure what needs to be done more .. please advice.
My understanding is that as long as maintainer is not replying procedure with create fesco trac ticket can be started.

As mentioned in the xml-security-c thread on the devel list, and again in the ticket #1699 about that package, and again here in this ticket, there is a very specific policy for dealing with non-responsive package maintainers. This is not a "close enough" thing, the policy needs to be followed exactly. This exact wiki page has been linked to you at least 3 times now. Please follow it if you wish for FESCo to respond.

I just came here to file a FESCo ticket myself concerning the "mc" issue.

Around 4 weeks ago (+/- a few days) someone made a mc.spec change that introduces:

a) a new mc upstream version (which is of course always welcome)
b) a "library" change from slang to ncurses - which also affects stable Fedora

This spec change arrived in Fedora git, packages got build and pushed to all active releases of Fedora (24/25/26/rawhide). A few karma-points has been given and the packages have shown up in all stable repositories. From my perspective no further testing has been done besides some "eyesight".

Unfortunately the changes of said library has introduced a lot of errors and misbehaviours of the program. Key, Keycombos, Modifiers etc. are absolutely misbehaving and in certain circumstances even cause fatal data loss.

More on that within the specified bug reports: e.g. Shift+F6 used to be rename, now it deletes (and in worst case if the setting was unset in mc setting -> deleting takes place without feedback).

The issues has been brought up even on the "mc" bugtracker, which had caused a few irritations and then brought up on fedoras bugzilla.

From what I learned so far: There was an intention to reduce dependencies and thus moving as much packages away from using slang. The goal was to move the packages from slang to ncurses.

Even if this goal is understandable, the final result of "mc" is that it is useless now. Even the description of the keybar (within mc) doesn't fit the keyactions (within mc) anymore.

The issue has been brought up on three different bugreports (from my knowledge). Besides discussing the technicals - a new spec file has been created that reverts this change. Unfortunately the new spec never made it into the git tree of Fedora "mc".

We are all waiting for some actions from the package maintainer (for aprox. 3 weeks now). Besides no further actions, more and more people find their way to the bugtracker complaining about missbehaving keyactions of "mc" etc..

Please note that even stable versions of Fedora are affected by this. Even my request to unpush the packages remained unheard.

http://midnight-commander.org/ticket/3254
https://bugzilla.redhat.com/show_bug.cgi?id=1440110
https://bugzilla.redhat.com/show_bug.cgi?id=1436394
https://bugzilla.redhat.com/show_bug.cgi?id=1442842

Thanks

I'd like to correct the mc upstream ticket to point to the correct cone:

http://midnight-commander.org/ticket/3807

I would also like to emphasize the importance of mc as a daily working tool.

Btw: Getting an 500 error when updating the issue... Sorry for duplicates...

Few clarifications:
1) not someone submitted patch with switching mc from slang to ncurses but it was me
2) I did suggested to propagate this change to all stable branches
3) Bug was found in QA stage but reports abut found issue seems where ignored
https://bugzilla.redhat.com/show_bug.cgi?id=1436394
4) mc with ncurses does not breaks anything. Seems SLang has tons of hacks/workarounds which should solved in terminals definitions in ncurses. As long as they will be not solved in ncurses definitions they will be affecting other ncurses using applications. Temporarily better is to go back to use SLang and patch doing this adds %bcond which will allow easier diagnose and fix ncurses issues
5) I have no time now to track all found issues with keys mapping and this is why I've submitted patch reverting to SLang. Probably will be able to back to investigate this issue within next week.

CC mc maintainers @jnovy @limb

Hi! Not actually an mc maintainer, but I have some comments.

First, I simply did a brief test, committed and built 4.8.19. Obviously my testing was painfully inadequate, and I'm sorry for that. Fortunately, the only release it went to stable on is f25: f26 and f24 still have it in testing.

That said, since I'm not an mc maintainer, I was unaware that this hadn't yet been corrected. If someone has a well-tested patch to revert to ncurses, I would be happy to help commit and build.

At the moment most important is go back to SLang and patch doing this is in https://bugzilla.redhat.com/show_bug.cgi?id=1442842
I just uploaded corrected version of the spec patch agree with suggestion send to me privately that %bcond name should be different.
Restore of the proper mc maintenance can be done later so if anyone has RW permission please review and commit attached patch.

Making the mistakes is not kind of critical issue, and as the author of the the patch introducing change to start use ncurses I made mistake here as well :(
Repeating mistakes is something which cannot have excuse ..
Looks like lack of quickly responding maintainer is something which is kind of bottleneck. Without such person even simple update on next official source tree release may be risky.
At the moment looks looks like there is no contact with current mc package maintainer and this issue must be resolved sooner or later as well.

I'm applying this patch and pushing updated builds. Please let me know if I can assist further.

Thx Jon :)

Closing the ticket as the issue with mc seems resolved. Please follow the steps jwboyer outlined in https://pagure.io/fesco/issue/1703#comment-438957 if you want to start the unresponsive maintainer process. Thanks for everybody involved!