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

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

Jun 17 '22 10:06 cemkeylan

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

Jun 19 '22 09:06 bnoordhuis

Should I create a duplicate issue over there?

Jun 19 '22 10:06 cemkeylan

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.

Jun 19 '22 10:06 bnoordhuis

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

Jun 25 '22 10:06 cemkeylan