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

File name too long for ustar when creating a tarball of the nodejs installation #130

Closed
cemkeylan opened this issue Jun 17, 2022 · 4 comments · Fixed by #224
Closed

File name too long for ustar when creating a tarball of the nodejs installation #130

cemkeylan opened this issue Jun 17, 2022 · 4 comments · Fixed by #224

Comments

@cemkeylan
Copy link

cemkeylan commented Jun 17, 2022

Version

v18.4.0

Platform

Linux dell-carbs 5.15.10 #7 SMP Tue Jan 18 15:17:48 +03 2022 x86_64 Carbs Linux

Subsystem

No response

What steps will reproduce the bug?

Create a tarball of the installed files using a standards-compliant tar or pax program.

./configure \
    --prefix=/usr \
    --ninja

ninja -C out/Release
tools/install.py install pkg /usr

tar -czf ninja.tar.gz pkg

or

pax -wz pkg > ninja.tar.gz

How often does it reproduce? Is there a required condition?

As long as the program follows the ustar format specifications, which limits file names to be 100 characters or less, it can be reproduced everytime. OpenBSD's implementation of tar is an example for this.

What is the expected behavior?

Creating a tarball without any errors.

What do you see instead?

tar: File name too long for ustar usr/lib/node_modules/corepack/dist/vendors-_yarn_berry_cache_proxy-agent-npm-5_0_0-41772f4b01-9_zip_node_modules_proxy-agent_index_js.js

Additional information

No response

@bnoordhuis
Copy link
Member

Should probably be moved to https://github.com/nodejs/corepack but I can't seem to move it there.

@cemkeylan
Copy link
Author

Should I create a duplicate issue over there?

@bnoordhuis
Copy link
Member

I'm hoping an org admin can move it but if you want to open a new issue and close this one, that's fine too, of course.

@richardlau richardlau transferred this issue from nodejs/node Jun 19, 2022
@cemkeylan
Copy link
Author

cemkeylan commented Jun 25, 2022

As a temporary measure I have renamed the file to be shorter and replaced the name in corepack.js which seems to be working fine when I enable corepack and use yarn

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 a pull request may close this issue.

2 participants