Skip to content
This repository has been archived by the owner on Apr 10, 2024. It is now read-only.

Can't update dependencies #52

Closed
TorstenStueber opened this issue Oct 4, 2021 · 2 comments
Closed

Can't update dependencies #52

TorstenStueber opened this issue Oct 4, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@TorstenStueber
Copy link
Member

Description
When updating the dependencies using the command cargo update, then a mysterious version conflict is reported.

Steps to Reproduce
Check out branch bridge-poc and un cargo update.

Expected vs. Actual Behavior
Expected behavior: no error reported.

Actual behavior: the following error is shown

pdating crates.io index
error: failed to select a version for `snow`.
    ... required by package `libp2p-noise v0.29.0`
    ... which is depended on by `libp2p v0.34.0`
    ... which is depended on by `sc-cli v0.9.0`
    ... which is depended on by `frame-benchmarking-cli v3.0.0`
    ... which is depended on by `pendulum-node v3.0.0 (/Users/torsten/Documents/development/satoshipay/pendulum/pnd-tmp/node)`
versions that meet the requirements `^0.7.1` are: 0.7.2, 0.7.1

all possible versions conflict with previously selected packages.

  previously selected package `snow v0.7.1`
    ... which is depended on by `libp2p-noise v0.29.0`
    ... which is depended on by `libp2p v0.34.0`
    ... which is depended on by `sc-cli v0.9.0`
    ... which is depended on by `frame-benchmarking-cli v3.0.0`
    ... which is depended on by `pendulum-node v3.0.0 (/Users/torsten/Documents/development/satoshipay/pendulum/pnd-tmp/node)`

failed to select a version for `snow` which could resolve this conflict

What is strange is that this version conflict does not seem to make any sense: it indicates that version 0.7.1 conflicts with the requirement ^0.7.1, which allows for versions 0.7.2, 0.7.1 .

@TorstenStueber TorstenStueber added the bug Something isn't working label Oct 4, 2021
@morgueye4
Copy link
Contributor

morgueye4 commented Oct 6, 2021

looks like related to this

Also after checking for a while opened also this one

@TorstenStueber
Copy link
Member Author

Okay, thanks. Seems like the upstream link provides a solution. TL;DR: never execute a blanket cargo update in a Substrate project.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants