Slightly funny tar ball for openssl 1.1.1c ?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Slightly funny tar ball for openssl 1.1.1c ?

Dennis Clarke-2

I don't thing I have seen this before :

beta $ gzip -dc ../src/openssl-1.1.1c.tar.gz | tar -xf -
tar: pax_global_header: typeflag 'g' not recognized, converting to
regular file
beta $

Must be a gnu tar thing?

--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
Reply | Threaded
Open this post in threaded view
|

AW: Slightly funny tar ball for openssl 1.1.1c ?

Dr. Matthias St. Pierre
> -----Urspr√ľngliche Nachricht-----
> I don't thing I have seen this before :
>
> beta $ gzip -dc ../src/openssl-1.1.1c.tar.gz | tar -xf -
> tar: pax_global_header: typeflag 'g' not recognized, converting to
> regular file
> beta $
>
> Must be a gnu tar thing?

Hi Dennis,

it's not a bug, it's a feature.  ;-)

No seriously: it's the `git archive` command which is used to export the tree
into a tarfile. It adds an extended header containing the commit hash of the
commit which was exported. Older tar programs don't know how to deal
with that header and are a bit confused about it.

We had a similar discussion after 1.1.1b was released, it started here
https://mta.openssl.org/pipermail/openssl-users/2019-February/009936.html

see in particular reply
https://mta.openssl.org/pipermail/openssl-users/2019-February/009949.html

and the links to the LKML which it contains
https://lkml.org/lkml/2005/6/18/5
https://marc.info/?l=linux-kernel&m=111909182607985&w=2

HTH,
Matthias

Reply | Threaded
Open this post in threaded view
|

Re: AW: Slightly funny tar ball for openssl 1.1.1c ?

Dennis Clarke-2

>> beta $ gzip -dc ../src/openssl-1.1.1c.tar.gz | tar -xf -
>> tar: pax_global_header: typeflag 'g' not recognized, converting to
>> regular file
>> beta $
>>
>> Must be a gnu tar thing?
>
> Hi Dennis,
>
> it's not a bug, it's a feature.  ;-)
>
> No seriously: it's the `git archive` command which is used to export the tree
> into a tarfile. It adds an extended header containing the commit hash of the
> commit which was exported. Older tar programs don't know how to deal
> with that header and are a bit confused about it.

Yep.  Old POSIX tar just coughed up a one line pax_global_header file :

52 comment=97ace46e11dba4c4c2b7cb67140b6ec152cfaaf4


>
> We had a similar discussion after 1.1.1b was released, it started here
> https://mta.openssl.org/pipermail/openssl-users/2019-February/009936.html
>
> see in particular reply
> https://mta.openssl.org/pipermail/openssl-users/2019-February/009949.html
>
> and the links to the LKML which it contains
> https://lkml.org/lkml/2005/6/18/5
> https://marc.info/?l=linux-kernel&m=111909182607985&w=2
>

Perfectly harmless feature.  Thank you for the detailed reply.

Dennis

Reply | Threaded
Open this post in threaded view
|

Re: Slightly funny tar ball for openssl 1.1.1c ?

Steffen Nurpmeso-2
Dennis Clarke wrote in <[hidden email]>:
 |
 |>> beta $ gzip -dc ../src/openssl-1.1.1c.tar.gz | tar -xf -
 |>> tar: pax_global_header: typeflag 'g' not recognized, converting to
 |>> regular file
 |>> beta $
 |>>
 |>> Must be a gnu tar thing?
 |>
 |> Hi Dennis,
 |>
 |> it's not a bug, it's a feature.  ;-)
 |>
 |> No seriously: it's the `git archive` command which is used to export \
 |> the tree
 |> into a tarfile. It adds an extended header containing the commit \
 |> hash of the
 |> commit which was exported. Older tar programs don't know how to deal
 |> with that header and are a bit confused about it.
 |
 |Yep.  Old POSIX tar just coughed up a one line pax_global_header file :
 |
 |52 comment=97ace46e11dba4c4c2b7cb67140b6ec152cfaaf4
 |
 |> We had a similar discussion after 1.1.1b was released, it started here
 |> https://mta.openssl.org/pipermail/openssl-users/2019-February/009936.html
 |>
 |> see in particular reply
 |> https://mta.openssl.org/pipermail/openssl-users/2019-February/009949.html
 |>
 |> and the links to the LKML which it contains
 |> https://lkml.org/lkml/2005/6/18/5
 |> https://marc.info/?l=linux-kernel&m=111909182607985&w=2
 |
 |Perfectly harmless feature.  Thank you for the detailed reply.

Does not look harmless on some BSD unless thorougly inspected
iirc.  Since 2013-09-13 ([9c1375a7]) i thus repack balls

      # Repack with standard tar(1) to avoid new-style headers
      ${git} archive --format=tar --prefix="${PROGRAM}-${REL}/" v${REL}.ar |
         ( cd "${TMPDIR}" && ${tar} -x -f - )
      cd "${TMPDIR}"

      ${tar} -c -f "${PROGRAM}-${REL}.tar" "${PROGRAM}-${REL}"

NetBSD tar for example might say[1], which is frightening.

    "%s extended headers posix ustar archive."
                    " Extracting as plain files. Following files might be"
                    " in the wrong directory or have wrong attributes.",

  [1] http://cvsweb.netbsd.org/bsdweb.cgi/src/bin/pax/tar.c?rev=1.75&content-type=text/x-cvsweb-markup&only_with_tag=MAIN

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)