Do not set a default value to struct fileystem.xfer_align and related
variables when we could not get a filesystem alignment because of a lack
of statfs/statvfs family of functions to know what we can trust the alignment.
Reduce performing fchdir().
For example, when the disk read object was opened with
archive_read_disk_open("file.txt")(not a directory),
performing fchdir() is really unneeded.
Avoid the difference between posix and Windows about behavior of
directory traversals; posix version changes working directory
everywhere while traversing a directory tree, but Windows version
does not at all. The difference will probably make user confused.
Change posix version behavior close to Windows version by restoring
working directory when the function returns. This change includes
the intention removing chdir() operation by using openat()-style
operations if the platform supports it.
Set PATH_MAX to the size the 2nd argument of getcwd function instead of zero.
If the size is zero, Solaris getcwd will return NULL because
the size will be used for malloc argument as allocating memory
size.
Update a test for directory traversals;
1. add a test for archive_read_disk_set_symlink_hybrid(),
2. add a test for archive_read_disk_set_symlink_logical().
Tim Kientzle [Sat, 8 Jan 2011 22:15:08 +0000 (17:15 -0500)]
As discussed in Issue 125, we're misusing CHECK_SYMBOL_EXISTS to
test the usability of various functions. CHECK_SYMBOL_EXISTS
doesn't attempt to link anything, so can't verify that the symbol
is actually present in libraries.
In particular, this causes problems in some cross-compile
environments (such as the LSB build environment), where the
system headers may define some symbols (such as major()) that
can't be linked against the cross libraries.
Change a compression type of test_compat_mac_gnutar.tgz.uu from gzip
to compress so that test_compat_mac_gnutar does not fail on Windows platform,
which does not have libz by default.
Tim Kientzle [Sun, 2 Jan 2011 20:03:04 +0000 (15:03 -0500)]
Extend tar/test/test_option_r to verify the bug that Michihiro found
with -r brokenness.
This turns out to be a bug in the core archive_read I/O not correctly
tracking the current file position under some circumstances.
Extend libarchive/test/test_read_position to verify file position
tracking both with and without a registered skip function.
Fix the bug: When libarchive falls back to regular reads to fill
out an internal skip request, it failed to count those
bytes toward the current file position.
Tim Kientzle [Sun, 2 Jan 2011 19:16:59 +0000 (14:16 -0500)]
Extend the test of bsdtar -r to exercise larger file contents.
This does not reproduce the problem that Michihiro recently found,
but it's an improvement in the test, so it's worth checking in.
Tim Kientzle [Fri, 31 Dec 2010 17:57:48 +0000 (12:57 -0500)]
Support --numeric-owner for tar extraction as well as archive creation.
This just involves reworking tar's extraction routines slightly to use
archive_read_extract2() with a custom-configured archive_write_disk
object, instead of the more convenient archive_read_extract()
interface that automatically builds a standard archive_write_disk
object.
Currently, this code supports STORE and MSZIP.
This reader always decompress recorded data even if archive_read_data
function is not called at all, because all blocks, which are
splited in 32768 bytes of uncompresssed data, need uncompressed
data of previous block to be decompressed, and there is no chance
that the format reader in libarchive knows that a caller application
such as bsdtar performs listing up filenames or finding one to
extract a specific file.
Tim Kientzle [Sat, 11 Dec 2010 18:56:34 +0000 (13:56 -0500)]
Fix a test that breaks on systems where GID 17 is actually
used. Leave comments about some additional cases that would
be nice to test if someone can figure out a good way to do
so (a way that won't break on Windows, for example).
Fix issue 119.
Change the file location check that a file location does not exceed
volume block. New one is that a file content does not exceed volume
block(end of an ISO image). It is better than previous check even
if the issue did not happen.
While reading an ISO image generated by an older version of mkisofs
utility, a file location indicates the end the ISO image if its file
size is zero and it is the last file of all files of the ISO image,
so it is possible that the location value is the same as the number
of the total block of the ISO image.
Fix issue 119.
Change the file location check that a file location does not exceed
volume block. New one is that a file content does not exceed volume
block(end of an ISO image). It is better than previous check even
if the issue did not happen.
While reading an ISO image generated by an older version of mkisofs
utility, a file location indicates the end the ISO image if its file
size is zero and it is the last file of all files of the ISO image,
so it is possible that the location value is the same as the number
of the total block of the ISO image.
Tim Kientzle [Tue, 7 Dec 2010 05:02:31 +0000 (00:02 -0500)]
Don't try to copy entry data if the entry has zero size.
In particular, this causes "Cannot write to empty file" errors
when extracting GNU tar extended 'D' directory entries.
Tim Kientzle [Sun, 5 Dec 2010 20:50:03 +0000 (15:50 -0500)]
First part of the NFS4 ACL support.
This renames a few things to acknowledge that there really
is more than one kind of ACL in the world and extends
the basic ACL storage to support the NFS4/NTFS ACL
mode bits. The ACL storage has also gained some
error checks to ensure that a single ACL does not have
both NFS4/NTFS and POSIX.1e ACEs.
Tim Kientzle [Sun, 5 Dec 2010 20:30:23 +0000 (15:30 -0500)]
Merge r2811 from trunk: Don't try to verify that compression-level=0
produces larger results than the default compression, since this isn't
true for all versions of liblzma.
Tim Kientzle [Sun, 5 Dec 2010 20:28:34 +0000 (15:28 -0500)]
Don't assert that compression-level=0 produces larger file
than the default compression, since the actual result varies
depending on the version of liblzma.
Tim Kientzle [Mon, 29 Nov 2010 02:50:17 +0000 (21:50 -0500)]
Restore ACLs after calls to chmod().
In particular, current versions of ZFS on Solaris and
FreeBSD erase ACLs on each call to chmod, so ACL
restore has to follow chmod calls on those platforms.
projects / thirdparty / libarchive.git / log
