On Oct 13, 2014, at 10:38 AM, Magnus Holmgren holmg...@debian.org wrote:
The
difference is that ustar is followed by two spaces, whereas in tar files
created by libtar it's followed by a null character.
The history behind this may help make it clearer:
There has been a POSIX standard for
On Feb 21, 2012, at 3:40 AM, Pino Toscano wrote:
Hi,
(greetings from your favourite Hurd porter)
Alle lunedì 13 febbraio 2012, Tim Kientzle ha scritto:
So on hurd, I see a couple of interesting failures for bsdtar:
[...]
Actually, libarchive is pretty fine on Hurd, as it was after I
as well), that would be appreciated.
Thanks,
Tim Kientzle
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Each of these reports includes the name of the test directory, e.g.,
Details for failing tests: /tmp/libarchive_test.2012-02-06T23.02.12-000
Can we get the contents of those directories (which include detailed
logs for each failure, the files involved, and other details)?
Tim
On Feb 9,
On Aug 13, 2011, at 10:29 AM, Paul Eggert wrote:
On 08/08/2011 03:28 AM, Thayne Harbaugh wrote:
Attached is a patch that allows archives to be created with
arbitrary owner or group names.
Thanks for the bug report and patch; I was unaware of the problem.
This runs into another area that
Thomas,
It will be a day or two before I can dig deeply into this.
Unfortunately, it's been a while since I looked at that
part of the code in detail, but I don't recall libarchive
requiring all directories to precede all files and
I recall a bunch of test cases over the last couple of years
/password and /etc/group.
We're willing to consider arguments to the contrary;
please feel free to add your comments to the bug
linked to just above.
Cheers,
Tim Kientzle
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
I've filed a bug on libarchive.googlecode.com
to track this issue upstream:
http://code.google.com/p/libarchive/issues/detail?id=69
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
:
a) Has no limit on the length of a path argument
to system calls such as open(), stat(), etc.
b) Has some other way to determine that limit.
As soon as I get clarification on this issue, it will
be quite easy to fix.
Tim Kientzle
libarchive author and maintainer
--
To UNSUBSCRIBE, email
Carl Miller wrote:
On Sat, Jan 16, 2010 at 05:09:45AM +, Clint Adams wrote:
You mean something like this?
- (d-header.c_dev_min == min) )
+ (d-header.c_dev_min == min)
+ ((d-header.c_mode CP_IFBLK) != CP_IFBLK)
+ ((d-header.c_mode CP_IFCHR) !=
On Fri, Jan 15, 2010 at 08:06:54PM -0800, Carl Miller wrote:
cramfs takes a shortcut with device nodes, and assigns them all inode 1.
I presume it also assigns nlinks == 1?
When using cpio to copy files out of a cramfs image, cpio turns the second
and all subsequent copied device nodes into
don't know if SVr4 includes any
documentation for the format apart from the implementation
itself. I don't have access to SVr4 source code.
Cheers,
Tim Kientzle
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
work).
I think it would be good to compare to OpenSolaris cpio, being a third
independent implementation of cpio. At the moment I do not have access
to one, but I'll try to setup something today.
Let us know what you find.
Cheers,
Tim Kientzle
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
For Tim's reference: we're discussing pax here:
http://bugs.debian.org/42158
I think it would be good to compare to OpenSolaris cpio, being a third
independent implementation of cpio. At the moment I do not have access
to one, but I'll try to setup something today.
Oh, yeah. Gunnar Ritter's
Tim Kientzle wrote:
For Tim's reference: we're discussing pax here:
http://bugs.debian.org/42158
I think it would be good to compare to OpenSolaris cpio, being a third
independent implementation of cpio. At the moment I do not have access
to one, but I'll try to setup something today.
Oh
for hardlink management
within a single program.
Tim Kientzle
Daniel Kahn Gillmor wrote:
Tim Kientzle of FreeBSD (author of libarchive, attempting to CC here)
describes the cpio format here:
http://people.freebsd.org/~kientzle/libarchive/man/cpio.5.txt
This document states about the SRV4 (newc
formats.
It won't work well with some other formats where the length
does actually depend on the data.
Cheers,
Tim Kientzle
Original Message
Date: Thu, 7 Aug 2008 21:31:27 -0500
From: John Goerzen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED
Thibaut VARENE wrote:
On Fri, Aug 8, 2008 at 8:42 AM, Tim Kientzle [EMAIL PROTECTED] wrote:
Thibaut,
John Goerzen forwarded your idea to me.
You can actually implement this on top of the current libarchive
code quite efficiently. Use the low-level archive_write_open()
call and provide your
to avoid
this problem on all platforms. I'll get that fix into 2.5.4.
Thank you for your patience. I'll let you know as soon as I
have a candidate fix.
Cheers,
Tim Kientzle
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Good guess, but I don't think that explains anything, since
the order in which hardlinked files get stored doesn't matter.
(There are a few tests that do detailed format verification;
those would be affected by the order in which files get stored,
but none of those depend on the ordering of
illuminating.
If this doesn't shed any light, send me the contents
of /tmp/bsdtar_test_X/test_basic for one of the
failed tests. Maybe there are some other clues in there.
Cheers,
Tim Kientzle
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
.
This is a low priority for me right now, though I
do believe that I've factored the internals well
enough to make this a feasible project for someone
who knows nothing about libarchive. If anyone is
interested, let me know.
Tim Kientzle
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
Note the use of __xstat64/fopen64 for the working code instead of
__xstat/fopen for the non-working code. At this point I believed it had
something to do with the use of 64bit offsets (USE_FILE_OFFSET64) but
simply adding this define to the compiler commandline didn't fix the
issue.
I'm not
the
32-bit version, it won't work.
Apparently, httpd.h is somehow forcing your code to use the
32-bit stat, which is incompatible with libarchive.
Tim Kientzle
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Thibaut VARENE wrote:
bip 8192
Do I win?
bip 8192
Do I win?
bip 8192
(note, with libarchive 2, 'bip' (the output of archive_write) is 0,
which seems a bit more coherent).
Yes, libarchive 1 does return wrong values from archive_write.
As you observed, this bug is fixed in libarchive 2.
Tim
25 matches
Mail list logo
