tar-1.25

[bdubbs@…]

New version.

​ftp://ftp.gnu.org/gnu/tar/tar-1.25.tar.bz2

Noteworthy changes in this release:

• Fix extraction of empty directories with the -C option in effect.
• Fix extraction of device nodes.
• Make sure name matching occurs before eventual name transformation.

Tar 1.24 changed the ordering of name matching and name transformation so that the former saw already transformed file names. This made it impossible to match file names in certain cases. It is fixed now.

• Fix the behavior of tar -x --overwrite on hosts lacking O_NOFOLLOW.

• Improve the testsuite.

• Alternative decompression programs.

[Gilles Espinasse]

1.24 is broken even the test suite pass ok.

That command fail where every other tar version were ok tar -x -C /tmp -f /tmp/ipcop.tar tar: usr/lib/engines: Cannot mkdir: No such file or directory tar: usr/share/kbd/keymaps/i386: Cannot mkdir: No such file or directory tar: usr/share/kbd/keymaps/i386/dvorak: Cannot mkdir: No such file or directory tar: usr/share/kbd/keymaps/i386/qwertz: Cannot mkdir: No such file or directory tar: usr/share/kbd/keymaps/i386/fgGIod: Cannot mkdir: No such file or directory tar: usr/share/kbd/keymaps/i386/azerty: Cannot mkdir: No such file or directory ... tar: Exiting with failure status due to previous errors

[bdubbs@…]

I saw a similar report on the tar mailing list. It is not, strictly speaking, an LFS problem, but it is an upstream problem. We may want to just hold off a while ot see if this is addressed.

I've been following the bug-tar mailing list for about six months now. For a program that has been around about 30 years, it seems to have lots of problems.