Re: bad timestamps mc-4.8.19 copy from archive

2017-10-09 Thread Nerijus Baliunas
On Fri, 11 Aug 2017 04:53:25 -0400 Felix Miata  wrote:

> Actual behavior:
> All files from archive show current timestamps
> 
> Expected behavior:
> Files and directories inherit individual timestamps from archive

It was reported by me - 
https://mail.gnome.org/archives/mc-devel/2017-April/msg0.html
And fixed by Andrey Gursky - 
https://mail.gnome.org/archives/mc-devel/2017-April/msg6.html

I proposed to release 4.8.20 with the fix back in May.

Regards,
Nerijus
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel


Re: bad timestamps mc-4.8.19 copy from archive

2017-08-11 Thread Andrew Borodin
On Fri, 11 Aug 2017 05:37:17 -0400 Felix Miata wrote:
> Yury V. Zaytsev composed on 2017-08-11 11:04 (UTC+0200):
> 
> > Felix Miata wrote:
> ...
> >> Reverting to 4.8.17 solves.
> 
> > Please check current git, should be already solved.
> 
> No luck searching. I get 15k hits searching for 'timestamp archive'. It wants 
> to
> search all of git across all repos rather than limiting to mc, and
> https://midnight-commander.org/search finds only one closed two year old bug.

https://midnight-commander.org/ticket/3821

-- 
Andrew
___
mc mailing list
https://mail.gnome.org/mailman/listinfo/mc


Re: bad timestamps mc-4.8.19 copy from archive

2017-08-11 Thread Felix Miata
Yury V. Zaytsev composed on 2017-08-11 11:04 (UTC+0200):

> Felix Miata wrote:
...
>> Reverting to 4.8.17 solves.

> Please check current git, should be already solved.

No luck searching. I get 15k hits searching for 'timestamp archive'. It wants to
search all of git across all repos rather than limiting to mc, and
https://midnight-commander.org/search finds only one closed two year old bug.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
mc mailing list
https://mail.gnome.org/mailman/listinfo/mc


Re: bad timestamps mc-4.8.19 copy from archive

2017-08-11 Thread Yury V. Zaytsev

On Fri, 11 Aug 2017, Felix Miata wrote:


Anyone else using openSUSE or Fedora seeing this:

To reproduce:
1-left pane, enter some tar.gz or .bz2 archive, e.g.
https://archive.mozilla.org/pub/seamonkey/releases/2.48/contrib/seamonkey-2.48.en-US.linux-x86_64.tar.bz2
saved locally
2-select all files with * key and dirs with INS
3-F5 -> ENTER
4-TAB

Actual behavior:
All files from archive show current timestamps

Expected behavior:
Files and directories inherit individual timestamps from archive

I first noticed this some weeks ago when busy and no time to follow-up before
forgetting. Tonight I updated two TW systems, then found a BS package for Fedora
25 and tried. All three suffer this. I recognize nothing in changelog or mc's
tracker to explain it as expected behavior. Ordinary copy continues to work as
expected. :-(

Reverting to 4.8.17 solves.


Please check current git, should be already solved.

--
Sincerely yours,
Yury V. Zaytsev
___
mc mailing list
https://mail.gnome.org/mailman/listinfo/mc


bad timestamps mc-4.8.19 copy from archive

2017-08-11 Thread Felix Miata
(I mistakenly sent to non-devel list.)

Anyone else using openSUSE or Fedora seeing this:

To reproduce:
1-left pane, enter some tar.gz or .bz2 archive, e.g.
https://archive.mozilla.org/pub/seamonkey/releases/2.48/contrib/seamonkey-2.48.en-US.linux-x86_64.tar.bz2
saved locally
2-select all files with * key and dirs with INS
3-F5 -> ENTER
4-TAB

Actual behavior:
All files from archive show current timestamps

Expected behavior:
Files and directories inherit individual timestamps from archive

I first noticed this some weeks ago when busy and no time to follow-up before
forgetting. Tonight I updated two TW systems, then found a BS package for Fedora
25 and tried. All three suffer this. I recognize nothing in changelog. Ordinary
copy continues to work as
expected. :-(

I find Trac difficult to use for searching. Is there an open bug for this? I
didn't find one, but I don't know if I'm searching it right.

Reverting to 4.8.17 solves.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel


bad timestamps mc-4.8.19 copy from archive

2017-08-11 Thread Felix Miata
Anyone else using openSUSE or Fedora seeing this:

To reproduce:
1-left pane, enter some tar.gz or .bz2 archive, e.g.
https://archive.mozilla.org/pub/seamonkey/releases/2.48/contrib/seamonkey-2.48.en-US.linux-x86_64.tar.bz2
saved locally
2-select all files with * key and dirs with INS
3-F5 -> ENTER
4-TAB

Actual behavior:
All files from archive show current timestamps

Expected behavior:
Files and directories inherit individual timestamps from archive

I first noticed this some weeks ago when busy and no time to follow-up before
forgetting. Tonight I updated two TW systems, then found a BS package for Fedora
25 and tried. All three suffer this. I recognize nothing in changelog or mc's
tracker to explain it as expected behavior. Ordinary copy continues to work as
expected. :-(

Reverting to 4.8.17 solves.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/
___
mc mailing list
https://mail.gnome.org/mailman/listinfo/mc