mc version unknown


Recommended Posts

There is something funky with midnight commander in V5.0.0

 

If you ask it the version you get:

 

mc -V
GNU Midnight Commander unknown
Virtual File Systems: tarfs, extfs, cpiofs, ftpfs, fish, smbfs
With builtin Editor
Using system-installed S-Lang library with terminfo database
With subshell support as default
With support for background operations
With mouse support on xterm and Linux console
With support for X11 events
With internationalization support
With multiple codepages support
Data types: char: 8; int: 32; long: 32; void *: 32; size_t: 32; off_t: 64;

 

 

a similar test on Debian 7.2

mc -V
GNU Midnight Commander 4.8.3
Built with GLib 2.32.4
Using the S-Lang library with terminfo database
With builtin Editor
With subshell support as default
With support for background operations
With mouse support on xterm and Linux console
With support for X11 events
With internationalization support
With multiple codepages support
Virtual File Systems: cpiofs, tarfs, sfs, extfs, ext2undelfs, ftpfs, fish
Data types: char: 8; int: 32; long: 64; void *: 64; size_t: 64; off_t: 64;

Link to comment

Does the same thing in 4.7.  This "bug" has been there for a very long time.  In looking at the source, the makefile wants to use git to grab the version from a commit tag.  I'm guessing that perhaps Patrick V. (slackware guy) didn't have git installed when these packages were built and no one has ever noticed... except for sharp-eyed NAS  ;)

 

Interesting in unraid 6, based on slack 14.1, it does seem to report the version:

 

root@develop64:~# mc -V
GNU Midnight Commander 4.8.9
Built with GLib 2.36.3
Using the S-Lang library with terminfo database
With builtin Editor
With subshell support as default
With support for background operations
With mouse support on xterm and Linux console
With support for X11 events
With internationalization support
With multiple codepages support
Virtual File Systems: cpiofs, tarfs, sfs, extfs, ftpfs, fish, smbfs
Data types: char: 8; int: 32; long: 64; void *: 64; size_t: 64; off_t: 64;

Link to comment

Interesting indeed.

 

I suppose it is not really a bug other than it makes it hard to check release logs and see if the mc feature or fix you need is included in unRAID.

 

Maybe we just close this by listing the version included in the current release

 

Edit: I just realised i never posted why i got  into this. mc seems to be incorrectly auto guessing if the "preserve attributes" flag should be unticked sometimes. Obviously this is a complete pain if you don't notice and don't re tick it. I know some work was done on this by the mc team but I cant tell if we are up to date to really start debugging it.

Link to comment