-
Notifications
You must be signed in to change notification settings - Fork 188
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
nimble install
doesn't respect newly downloaded packages.json
#953
Comments
Merged
It appeared in Nim repo CI too.
|
I just tested this again and had the same issue |
@dom96 if you didn't see this ^ the issue should be re-opened |
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Aug 8, 2022
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Aug 9, 2022
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Aug 9, 2022
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Aug 9, 2022
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Aug 9, 2022
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Aug 9, 2022
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. In order that change to work we have to add nim package in nimble packages repo and also add alias compiler -> nim to avoid breaking backward compatibility. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Aug 10, 2022
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. In order that change to work we have to add nim package in nimble packages repo and also add alias compiler -> nim to avoid breaking backward compatibility. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Aug 10, 2022
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. In order that change to work we have to add nim package in nimble packages repo and also add alias compiler -> nim to avoid breaking backward compatibility. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Aug 10, 2022
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. In order that change to work we have to add nim package in nimble packages repo and also add alias compiler -> nim to avoid breaking backward compatibility. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Aug 10, 2022
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. In order that change to work we have to add nim package in nimble packages repo and also add alias compiler -> nim to avoid breaking backward compatibility. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Aug 11, 2022
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. In order that change to work we have to add nim package in nimble packages repo and also add alias compiler -> nim to avoid breaking backward compatibility. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Sep 12, 2022
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. In order that change to work we have to add nim package in nimble packages repo and also add alias compiler -> nim to avoid breaking backward compatibility. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Sep 12, 2022
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. In order that change to work we have to add nim package in nimble packages repo and also add alias compiler -> nim to avoid breaking backward compatibility. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Dec 21, 2022
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. In order that change to work we have to add nim package in nimble packages repo and also add alias compiler -> nim to avoid breaking backward compatibility. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Jan 3, 2023
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. In order that change to work we have to add nim package in nimble packages repo and also add alias compiler -> nim to avoid breaking backward compatibility. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Jan 4, 2023
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. In order that change to work we have to add nim package in nimble packages repo and also add alias compiler -> nim to avoid breaking backward compatibility. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Jan 4, 2023
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. In order that change to work we have to add nim package in nimble packages repo and also add alias compiler -> nim to avoid breaking backward compatibility. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Jan 4, 2023
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. In order that change to work we have to add nim package in nimble packages repo and also add alias compiler -> nim to avoid breaking backward compatibility. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Jan 19, 2023
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. In order that change to work we have to add nim package in nimble packages repo and also add alias compiler -> nim to avoid breaking backward compatibility. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
yyoncho
added a commit
to yyoncho/nimble
that referenced
this issue
Feb 1, 2023
- Fixes nim-lang#953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. In order that change to work we have to add nim package in nimble packages repo and also add alias compiler -> nim to avoid breaking backward compatibility. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
zah
pushed a commit
that referenced
this issue
Feb 13, 2023
- Fixes #953 Allow having nim as locked dependency. - I will add unit tests once we agree on the approach and once nimble related changes in nim are merged (I will link the PR in comment). Ditto for the documentation. In order that change to work we have to add nim package in nimble packages repo and also add alias compiler -> nim to avoid breaking backward compatibility. Here it is the flow: ``` bash nimble develop nim nimble lock ``` After that `nimble install` and `nimble build` commands will use the locked `nim` version
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a package is not found,
and prompted to download a new list from the internet,
the package will still be reported as "not found'
(even if it was in the newly downloaded list).
I experienced this with
chipmunk7
,which was recently added to the list.
nimble install chipmunk7
worked the second time I tried the command.The text was updated successfully, but these errors were encountered: