[mc] corrupt timestamps on files copied from archives
According to https://mail.gnome.org/archives/mc/2017-August/msg00003.html this problem was fixed upstream ~2 months before MGA6 release by https://midnight-commander.org/ticket/3821 but I am unable to understand the dev-speak in that bug report to confirm.
Fix needs to be included in 4.8.19 as MGA6 update, or MGA6 package updated to 4.8.20, as attempting to install 4.8.20 from MGA7 using rpm manually is inexplicably blocked by "required" perl-base upgrade.
From the mc mailing list thread:
1-left pane, enter some tar.gz or .bz2 archive, e.g.
2-select all files with * key and dirs with INS
3-F5 -> ENTER
All files from archive show current timestamps
Files and directories inherit individual timestamps from archive
Reverting to 4.8.17 solves.
Assigning to all packagers collectively, since there is no registered maintainer for this package.
CC'ing daviddavid, who pushed mc most often in the past few years
Midnight Commander has been updated to fix an issue with corrupt timestamps when extracting from an archive.
Uploaded to core/updates_testing:
MGA6-32 on IBM Thinkpad R50e Xfce
No installation issues.
Confirm that file and folder selected from seamonkey archive above preserve the original timestamp 7 July 2017 when copied with mc.
OK for me.
Tried M6 x64, but with: mc-4.8.19-1.mga6 PRE update
I could not reproduce the described problem. Copying with MC as described in comment 0 a .tar.gz or .bz archive to another directory always preserved the file timestamps as in the archive.
So live with Herman's OK result.
An update for this issue has been pushed to the Mageia Updates repository.