Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#79400 - [mc] 4.8.30-1 tar VFS corruption bug

Attached to Project: Arch Linux
Opened by Toolybird (Toolybird) - Thursday, 17 August 2023, 08:43 GMT
Last edited by Toolybird (Toolybird) - Sunday, 27 August 2023, 20:54 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

This is basically a "heads up" because I haven't quite figured out any rhyme or reason yet. But there appears to be a bizarre bug with the latest mc involving tar archives.

I'd be grateful if any mc user could try to reproduce the error I'm seeing.

Steps to reproduce:

1. open mc and navigate to "/var/cache/pacman/pkg"
2. open (press enter) on "gcc-13.1.1-2-x86_64.pkg.tar.zst"
3. navigate to "/usr/bin" inside the archive
3. "tab" across to opposite panel and navigate to "/tmp"
4. "tab" back to archive and copy (press F5) on "gcc" to copy the gcc binary to /tmp
5. now run "file /tmp/gcc"

$ file /tmp/gcc
/tmp/gcc: POSIX tar archive

It's *NOT* an ELF binary!

It all works fine with mc-4.8.29-2

The NEWS file mentions:
* tar: support extended headers (including long file names and sparse files) (#1952, #2201)

Any ideas?
This task depends upon

Closed by  Toolybird (Toolybird)
Sunday, 27 August 2023, 20:54 GMT
Reason for closing:  Upstream
Additional comments about closing:  See comments
Comment by V.S. (vence) - Saturday, 19 August 2023, 09:55 GMT
I got the same issue for gcc-13.2.1 (all binary files EXCEPT cpp, gcov, gcov-tool) and gcc-fortran-13.2.1 (both binary files). However, I examined several other packages (e.g. gdb, make, mc, vim) and made several *.tar.zst archives -- and everything was fine. It's a mystery. No ideas.
Comment by Toolybird (Toolybird) - Sunday, 20 August 2023, 10:58 GMT
https://midnight-commander.org/ticket/4494

hardlinks are the problem
Comment by Toolybird (Toolybird) - Sunday, 27 August 2023, 20:54 GMT
Fixed upstream [1]. We'll get it at next release.

[1] https://github.com/MidnightCommander/mc/commit/a4a5c97e1f1b4ffad251cc5278e3895c3ca2336d

Loading...