composer: Warn about identical names with different capitalization on zip archive extract failure (Not a directory)
When unzip fails with “checkdir error: [path] exists but is not a directory” or if ZipArchive->extractTo fails with ErrorException ZipArchive::extractTo(): Not a directory we should display a message warning that the archive may contain a directory and a file with the same name but different capitalization which fails to extract on case insensitive filesystems.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 15 (6 by maintainers)
Commits related to this issue
- Warn identical names w/ different capitalization - extract zip archive Warn about identical names with different capitalization on zip archive extract failure (Not a directory) Issue #5938 — committed to composer/composer by theikalman 7 years ago
- Warn identical names w/ different capitalization - extract zip archive Warn about identical names with different capitalization on zip archive extract failure (Not a directory) Issue #5938 — committed to svenmuennich/composer by theikalman 7 years ago
- Warn identical names w/ different capitalization for unzip Warn about identical names with different capitalization on unzip archive extract failure (Not a directory) Issue #5938 — committed to svenmuennich/composer by theikalman 7 years ago
If you notice this problem again or you still have this problem try to clear composer cache first:
composer clearcacheHi, i have the solution.
You only need delete in c:\program file\7-Zip,
after you need, reinstall this software. 7-zip
after execute
laravel new your_app
and ready.
Hi! As far as I understand - in this case, the problem is related to the ratio of Windows to the register. Those. if your OS is Windows, and you work through the Linux console, then the relationship to the register will be from Windows, since the console will work on the basis of Windows. I’m currently working on a Laravel project and I’m using docker to set up a virtual environment. When I encountered this problem, I realized that the raised environment should not be accessed through the Linux console running at the root of the project, but directly through the docker console, so to speak, from inside the raised system. It helped me, it might help you too. Good luck.