-
Notifications
You must be signed in to change notification settings - Fork 191
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
nim says "invalid package name" #940
Comments
Related: nim-lang/Nim#18840 |
Also, we should handle better/differently this error:
Maybe |
@narimiran This was my initial plan, but unfortunately, it cannot happen because the checksum of the package is calculated on the entire package content and not only on the installed files.
@dom96 Unfortunately the new functionality depends on a commit present only in the latest Nim version, in particular on the functionality added to the |
I don't think we can release it like this unfortunately. Preventing changing to an older Nim is a showstopper. I'm sure we can resolve this, the question is: how should we do it? |
This reverts commit f373c17. For more details, see: - nim-lang/nimble#940 - nim-lang#18840 - https://forum.nim-lang.org/t/8404
This reverts commit f373c17. For more details, see: - nim-lang/nimble#940 - #18840 - https://forum.nim-lang.org/t/8404
This reverts commit f373c17. For more details, see: - nim-lang/nimble#940 - #18840 - https://forum.nim-lang.org/t/8404 (cherry picked from commit 3d7c52f)
…im-lang#18872) This reverts commit f373c17. For more details, see: - nim-lang/nimble#940 - nim-lang#18840 - https://forum.nim-lang.org/t/8404
- Fixes nim-lang/nimble#940 - Fixes nim-lang#18840
I always cloned latest nim source and compiled in MSYS2+MingW64 on windows 10 64 bits. Everything is OK months ago. But now, something weired happened
nim.exe
andnimble.exe
I delete
C:\Users\USER\.nimble\
totallythe new
nim
compiler can compile the followinga.nim
without problemthe processing:
nimble
can install packageI found that the new-installed package is under
C:\Users\USER\.nimble\pkgs\listsv-0.1.0-a6dfb9de705011f6d04902493cac04a4f20a0435\
directory. However, I remember it should belistsv-0.1.0
. So what happened tonimble
?thanks
The text was updated successfully, but these errors were encountered: