Ticket #4624 (closed defect: invalid)
Unzip via MC of tar.xz file didn't working correctly
Reported by: | balemi | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | mc-vfs | Version: | 4.8.29 |
Keywords: | tar.xz | Cc: | |
Blocked By: | Blocking: | ||
Branch state: | no branch | Votes for changeset: |
Description
I probably spot a bug, once I try to unzip via MC file factorio-headless_linux_2.0.28.tar.xz
After unzip via F5 from .tar.xz file to system I got files:
elevated-rail-chain-signal-l
elevated-rail-chain-signal.l
elevated-rail-chain-signal-m
elevated-rail-chain-signal-s
rail-chain-signal-elevated.l
But once I try to unzip it via command:
tar -xvJf factorio-headless_linux_2.0.28.tar.xz
I got correct file names:
elevated-rail-chain-signal-lights.lua
elevated-rail-chain-signal.lua
elevated-rail-chain-signal-metals.lua
elevated-rail-chain-signal-shadow.lua
rail-chain-signal-elevated.lua
Can you please look into this?
My version is:root@nuc:/home/factorio# mc -V
GNU Midnight Commander 4.8.29
Built with GLib 2.74.5
Built with S-Lang 2.3.3 with terminfo database
Built with libssh2 1.10.0
With builtin Editor and Aspell support
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
With ext2fs attributes support
Virtual File Systems:
cpiofs, tarfs, sfs, extfs, ext2undelfs, ftpfs, sftpfs, fish
Data types:
char: 8; int: 32; long: 64; void *: 64; size_t: 64; off_t: 64;
Running on:PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
(reference of my issue in forum thread: https://forums.factorio.com/viewtopic.php?f=49&t=125543&p=657338#p657338 )
Recent version of mc is 4.8.32.
There was a large tar update in 4.8.30 (#1952, #2201).
Feel free to reopen this ticket if this bug is still actual for 4.8.32.