Skip to content
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

Restrict tar transform to regular files #24

Open
wants to merge 1 commit into
base: 2019.02-op-build
Choose a base branch
from

Conversation

madscientist159
Copy link

Without this restriction, symlinks are rewritten and corrupted.

Example without the restriction:

Input tree (valid):
package-githash/file1
package-githash/link -> ./file1

Output tree (broken):
package-githash/file1
package-githash/link -> package-githash/file1

Without this restriction, symlinks are rewritten and corrupted.

Example without the restriction:

Input tree (valid):
package-githash/file1
package-githash/link -> ./file1

Output tree (broken):
package-githash/file1
package-githash/link -> package-githash/file1
@sammj
Copy link

sammj commented Apr 23, 2019

Is this something that should go upstream as well?

@madscientist159
Copy link
Author

Yes, that is the intent of the pull request.

@sammj
Copy link

sammj commented Apr 26, 2019

I meant actual upstream Buildroot :) This looks sane but it would be good to be able to reference it going to Buildroot's development list (ie. http://lists.buildroot.org/mailman/listinfo/buildroot) as well.

@madscientist159
Copy link
Author

@sammj Sorry, didn't quite understand there at first 😄 I went ahead and sent it upstream as well.

@shenki
Copy link
Member

shenki commented Apr 29, 2019

Thank you for the patch.

I see that upstream asked you to use a different flag. Let me know when you've sent your v3, and I will apply that to our buildroot fork. If you cc me ([email protected]) I can review it too.

@madscientist159
Copy link
Author

Yes, the new flag is verified to work, v3 wasn't set yet since I need to figure out what the formatting problem is when sending the patches in.

@mdmillerii
Copy link

I need to figure out what the formatting problem is when sending the patches in.

@madscientist159 you need to place a blank line in the commit message after the subject before the body

Otherwise git will concatnate the lines then decide the subject is too long and you end up with your broken formatting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants