Mailing List Archive: tar-1.26 not unpacking archives with symlinks?

tar-1.26 not unpacking archives with symlinks?

Feb 29, 2012, 9:33 AM

Post #1 of 3 (1868 views)

Hi, I'm hitting an error when trying to unpack archives with the
recently unmasked tar-1.26. Basically any symlinks in the archive
trigger an "unknown file" error. This prevents me using emerge -k
amongst other things

I only see this on uclibc-0.9.33 based system, not on the build host
which uses glibc amd64

Can anyone else repro this and shed any light on what the problem might
be? Problem in tar or uclibc?

Thanks

Ed W

Re: tar-1.26 not unpacking archives with symlinks? [ In reply to ]

vapier at gentoo

Apr 1, 2012, 9:38 PM

Post #2 of 3 (1785 views)

Permalink

On Wednesday 29 February 2012 12:33:02 Ed W wrote:
> Hi, I'm hitting an error when trying to unpack archives with the
> recently unmasked tar-1.26. Basically any symlinks in the archive
> trigger an "unknown file" error. This prevents me using emerge -k
> amongst other things
>
> I only see this on uclibc-0.9.33 based system, not on the build host
> which uses glibc amd64
>
> Can anyone else repro this and shed any light on what the problem might
> be? Problem in tar or uclibc?

fchmodat() is a syscall that takes 3 args. uClibc was providing a stub that
treated it as 4. i fixed things up, so if you want to try with the fix i just
committed, that'd be nice ...
-mike

Re: tar-1.26 not unpacking archives with symlinks? [ In reply to ]

lists at wildgooses

Apr 3, 2012, 6:35 AM

Post #3 of 3 (1774 views)

Permalink

On 02/04/2012 05:38, Mike Frysinger wrote:
> On Wednesday 29 February 2012 12:33:02 Ed W wrote:
>> Hi, I'm hitting an error when trying to unpack archives with the
>> recently unmasked tar-1.26. Basically any symlinks in the archive
>> trigger an "unknown file" error. This prevents me using emerge -k
>> amongst other things
>>
>> I only see this on uclibc-0.9.33 based system, not on the build host
>> which uses glibc amd64
>>
>> Can anyone else repro this and shed any light on what the problem might
>> be? Problem in tar or uclibc?
> fchmodat() is a syscall that takes 3 args. uClibc was providing a stub that
> treated it as 4. i fixed things up, so if you want to try with the fix i just
> committed, that'd be nice ...
> -mike

Excellent - many thanks

Out of the country at present - will verify on my return

Again many thanks

Ed W

Mailing List Archive

Mailing List Archive

Attached Files: