Skip to content
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.

Sign up for GitHub

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

Jump to bottom

nimble install doesn't respect newly downloaded packages.json #953

Closed
avahe-kellenberger opened this issue Oct 11, 2021 · 3 comments · Fixed by #962 or #1017
Closed

nimble install doesn't respect newly downloaded packages.json #953

avahe-kellenberger opened this issue Oct 11, 2021 · 3 comments · Fixed by #962 or #1017

Comments

@avahe-kellenberger
Copy link

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.
@ire4ever1190 ire4ever1190 mentioned this issue Nov 30, 2021
Merged
dom96 pushed a commit that referenced this issue Dec 15, 2021
@ire4ever1190
Fix #953 (#962)
26c9102 
* Fix package download not using refreshed package list

* Added test

* Use exitCode to remove warning

* Use clearer identifier names (`ignorePackageCache` instead of `clean`)
@ringabout
Copy link
Member

It appeared in Nim repo CI too.

nimble install -y --nimbleDir:build/deps jester@#head
Downloading https://github.com/dom96/jester using git
  Verifying dependencies for jester@#head
 Installing httpbeast@>= 0.4.0
    Prompt: httpbeast not found in any local packages.json, check internet for updated packages? -> [forced yes]
Downloading Official package list
    Success Package list downloaded.
       Tip: 12 messages have been suppressed, use --verbose to show them.
     Error: Package not found.
FAILURE

cmd: echo runCI failed
runCI failed

@avahe-kellenberger
Copy link
Author

I just tested this again and had the same issue nimble v0.13.1 compiled at 2022-05-05 01:16:54 with the new array2d package

@avahe-kellenberger
Copy link
Author

@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
@yyoncho
Allow locking nim version in nimble.lock
a578aab 
- 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 yyoncho mentioned this issue Aug 8, 2022
Merged
yyoncho added a commit to yyoncho/nimble that referenced this issue Aug 9, 2022
@yyoncho
Allow locking nim version in nimble.lock
af14e5e 
- 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
@yyoncho
Allow locking nim version in nimble.lock
cce8137 
- 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
@yyoncho
Allow locking nim version in nimble.lock
7137452 
- 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
@yyoncho
Allow locking nim version in nimble.lock
cf302e2 
- 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
@yyoncho
Allow locking nim version in nimble.lock
045134d 
- 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
@yyoncho
Allow locking nim version in nimble.lock
3f8d087 
- 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
@yyoncho
Allow locking nim version in nimble.lock
b4b2ace 
- 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
@yyoncho
Allow locking nim version in nimble.lock
72cd1c3 
- 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
@yyoncho
Allow locking nim version in nimble.lock
11f85b7 
- 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
@yyoncho
Allow locking nim version in nimble.lock
567f6a5 
- 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
@yyoncho
Allow locking nim version in nimble.lock
1c86bad 
- 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
@yyoncho
Allow locking nim version in nimble.lock
f497257 
- 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
@yyoncho
Allow locking nim version in nimble.lock
a1bda0f 
- 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
@yyoncho
Allow locking nim version in nimble.lock
1c80809 
- 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
@yyoncho
Allow locking nim version in nimble.lock
ae5509c 
- 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
@yyoncho
Allow locking nim version in nimble.lock
a9110b5 
- 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
@yyoncho
Allow locking nim version in nimble.lock
c610846 
- 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
@yyoncho
Allow locking nim version in nimble.lock
2faa793 
- 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
@yyoncho
Allow locking nim version in nimble.lock
b1f4e76 
- 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
@yyoncho @zah
Allow locking nim version in nimble.lock
78aaf3d 
- 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
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix #953 ire4ever1190/nimble
Allow locking nim version in nimble.lock yyoncho/nimble
2 participants
@avahe-kellenberger @ringabout