From mrmazda at earthlink.net Wed Mar 18 00:50:49 2020 From: mrmazda at earthlink.net (Felix Miata) Date: Tue, 17 Mar 2020 20:50:49 -0400 Subject: displays bad regular file timestamps on entry to .bz2 file & preserves the errors on copy out Message-ID: <2ced9884-9854-3b51-f74a-512d2c1b4189@earthlink.net> It's only happened on this one so far that I can remember: Others I've checked from mozilla.org are handled normally. Tar has no such problem. Is this a known issue? I've not been able to find anything on point among tickets on https://midnight-commander.org/ -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ From aborodin at vmail.ru Sat Mar 21 07:48:30 2020 From: aborodin at vmail.ru (Andrew Borodin) Date: Sat, 21 Mar 2020 10:48:30 +0300 Subject: displays bad regular file timestamps on entry to .bz2 file & preserves the errors on copy out In-Reply-To: <2ced9884-9854-3b51-f74a-512d2c1b4189@earthlink.net> References: <2ced9884-9854-3b51-f74a-512d2c1b4189@earthlink.net> Message-ID: On Tue, 17 Mar 2020 20:50:49 -0400 Felix Miata via mc-devel wrote: > It's only happened on this one so far that I can remember: > > Others I've checked from mozilla.org are handled normally. > > Tar has no such problem. The most part of tar source code in MC is very old (end of 1990s or beginning of 2000s) and doesn't support some modern tar features. In the case of firefox-68.6.0esr.tar.bz2, MC's tar vfs ignores extended headers which contain the mtime of file in tar archive. The mtime field in POSIX header is 0, therefore you can see the the 1 Jan 1970 in MC file panel. > Is this a known issue? I've not been able to find anything on point among tickets > on https://midnight-commander.org/ Probably, the main tar ticket is https://midnight-commander.org/ticket/1952. -- Amdrew