-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove PaxHeaders from distributed package #18
Comments
hey tnx ... Interesting whenever I package the module I use puppet module command, but maybe was an older version. I will re-package it with the next release. tnx |
Awesome! 👍 |
@n1tr0g Can you do a 0.0.z point release to fix this? It's filling logs pretty quickly. Thanks! |
sure ... will do it tonight ... |
done version 1.2.2 released |
@n1tr0g Hrm, this still shows up with 1.2.2. I'm not sure what command you're using and what version of tar you have, but the problem persists. Perhaps a tar with different flags than puppet expects?
|
Hmmm than this must be a bug in tar. I am using OS X with puppet. My versions $ puppet --version $ tar --version $ sw_vers -productVersion Does this happen also on my other modules like influxdb ? |
Are you tarring up the file yourself, using |
I use puppet module build so it uses the default tar provided by OS X 10.10.5 which is bsdtar 2.8.3 - libarchive 2.8.3. For the immediate I will repack the module on a Ubuntu server, but I am definitely interested in the root cause of this issue. |
@n1tr0g It looks like it just depends on the tar used to package it whether or not PaxHeaders are included. On the receiving side, I see it because I use r10k and it uses minitar to unpack the archives. See puppetlabs/r10k#558, feature request to have minitar ignore the headers instead of alerting. |
ok repacked on ubuntu and tested it via r10k. The PaxHeaders warning are gone. tnx again for the patience. |
Hi @n1tr0g ,
I'm having an issue similar to this.
Can you please re-package and update the Forge?
Thank you,
Yarden
The text was updated successfully, but these errors were encountered: