You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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
orpax
program.or
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 oftar
is an example for this.What is the expected behavior?
Creating a tarball without any errors.
What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: