-
Notifications
You must be signed in to change notification settings - Fork 14
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
Regression between atlas in Nim 2.0.2 and Nim 2.0.8 : old hash commit with previous nimble formatting generate no nim.cfg file or empty nim.cfg file #126
Comments
If it's incorrect, what does it look like? |
Sorry I was short on details as I opened the issue from my phone to not forget about it. All these have been tested on OSX ARM CPU (M1 MacBook Pro). As a test, I run the following command on both version
This is the output for atlas compiled using :
and
By default, all the package are on the latest default branch. ======================================================================================= This is the output for atlas compiled using : This is the output:
Right away, the resolver change from MaxVer to SemVer. Because there are issue of old version taken by atlas I also tried the following steps with MaxVer instead of SemVer (no luck : same result).
This error seems to come from the nimble file :
=> The above error does not go away as long as the generated nimble is present and stops from generating a nim.cfg at all.
This error comes from atlas taking an old version (not sure why), even with Even when fixing that manually (deleting nimble file), the generated nim.cfg at the root of the workspace is empty :
|
Update : this might be package related, since doing
works and generate a correct nim.cfg. So to sum-up I see 2 issues :
|
This could be related to atlas fetching older version with a nimble file that has an old syntax. For example,
So far this seems the common denominator of all package that cause a problem. Did something change between 2.0.2 and 2.0.8 around the handling on nimble file in atlas ? |
Nothing changed but we can improve Atlas so that it doesn't even try to parse .nimble files starting with |
It would be a first step; something also changed in how version / commit hash are resolved and on 2.0.8 I get older commit (even on MaxVer which is odd) that don't compile. |
I upgraded from 2.0.2 to 2.0.8 and notice a severe regression :
atlas use
no longer generate a correct nim.cfg files.The text was updated successfully, but these errors were encountered: