-
Notifications
You must be signed in to change notification settings - Fork 373
opam pin fails on Windows #6472
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
Comments
It's unfortunately obvious what's wrong when looking at the debug output:
|
I don't think this has anything to do with pinning a sha - the issue is the path at https://github.com/rescript-lang/flow/tree/rescript/tests/long_directory_names/really_long_path/really_long_path/really_long_path/really_long_path/really_long_path/really_long_path/really_long_path/really_long_path/really_long_path/really_long_path/really_long_path. The fix here needs to be in the repo - committing a path that long is a bit like including non-Windows characters (e.g. filenames with The repo is just cloneable on Windows - it's just that the opam root and where the repo is then cloned to makes it too long. |
We should probably surface the error message from Git more clearly, though! |
Huh, I never expected that long path in the flow repository. Thank you for pointing it out! |
Maybe it is dangerous for Windows users that opam enables |
It's the same problem during the install process. This is the only error message I got
This has been resolved by removing the problematic directory. I think it happened while scanning the |
I trying to pin a package to a specific commit hash
This works well on my Linux/MacOS machine. But fails on Windows (GitHub actions)
https://github.com/cometkim/windows-action-test/actions/runs/14424847341/job/40452212688
The text was updated successfully, but these errors were encountered: