(Please CC me in the replies as I'm not subscribed)
Hello list,
examing the tarballs generated by "make dist" using "tar -tzvvf", it seems
that information about group/owner of the buildsystem is being leaked.
Example output - notice the jenkins/jenkins field:
# tar -tzvvf core/cfengine-3.7.
(Cross posting to both bug-automake and bug-tar as I can see both projects
being affected.)
(Please keep me CC'd as I'm not subscribed.)
Hello,
this bug report is because of the following messages when extracting a
source tarball generated with "make dist". You can read the full bug
report at
(Please keep me CC'd as I'm not subscribed.)
Hello list,
as the title says, I believe running "make dist" should fail when tar
fails. The problem is that because there is a shell pipeline with gzip,
the exit code of the pipeline is 0. I'm not aware of a portable way to fix
this (named pipes m
On 01/16/2015 08:01 AM, Dimitrios Apostolou wrote:
> (Please keep me CC'd as I'm not subscribed.)
In general, GNU list policy is to reply-to-all, precisely so you don't
have to leave disclaimers like that :)
>
> Hello list,
>
> as the title says, I believe running "make dist" should fail when t
On Fri, 16 Jan 2015, Eric Blake wrote:
On 01/16/2015 08:01 AM, Dimitrios Apostolou wrote:
Relevant output from "make V=1 dist":
tardir=cfengine-3.7.0a1.5ffcc54 && tar --format=ustar -chf - "$tardir" |
GZIP=--best gzip -c >cfengine-3.7.0a1.5ffcc54.tar.gz
It is portable to do something hairy li
Dimitrios Apostolou wrote:
Why is such behaviour desirable?
It's more logical, since it causes tar to behave as if the symlink were not
there, and the pointed-to file was there instead.
Using -hard-dereference bloats the tar image, but if that's a price you're
willing to pay then you have a
