Parity-ethereum: no matching package named `ring` found (required by `multihash`) version required: ~0.6.2 versions found: 0.9.7, 0.9.6, 0.9.5, ...

Created on 7 Jun 2017  路  15Comments  路  Source: openethereum/parity-ethereum

Apart from the fact that this needed almost 4 hours ... it failed:

date; cargo install --git https://github.com/paritytech/parity.git parity; date

Tue  6 Jun 17:49:12 BST 2017

    Updating git repository `https://github.com/paritytech/parity.git`
  Installing parity v1.7.0 (https://github.com/paritytech/parity.git#99bfef28)
    Updating registry `https://github.com/rust-lang/crates.io-index`
    Updating git repository `https://github.com/paritytech/rust-ctrlc.git`
    Updating git repository `https://github.com/paritytech/jsonrpc.git`
    Updating git repository `https://github.com/paritytech/nanomsg.rs.git`
    Updating git repository `https://github.com/paritytech/js-precompiled.git`
    Updating git repository `https://github.com/paritytech/hyper`
    Updating git repository `https://github.com/tailhook/rotor`
    Updating git repository `https://github.com/paritytech/rust-secp256k1`
    Updating git repository `https://github.com/paritytech/rust-rocksdb`
    Updating git repository `https://github.com/paritytech/bn`
    Updating git repository `https://github.com/tomusdrw/tokio-proto`
    Updating git repository `https://github.com/tomusdrw/tokio-minihttp`
    Updating git repository `https://github.com/nikvolf/parity-tokio-ipc`
    Updating git repository `https://github.com/tomusdrw/ws-rs`
    Updating git repository `https://github.com/alexcrichton/mio-named-pipes`
    Updating git repository `https://github.com/nikvolf/tokio-named-pipes`
    Updating git repository `https://github.com/paritytech/libusb-rs`
    Updating git repository `https://github.com/paritytech/hidapi-rs`
    Updating git repository `https://github.com/paritytech/libusb-sys`
error: failed to compile `parity v1.7.0 (https://github.com/paritytech/parity.git#99bfef28)`, intermediate artifacts can be found at `/tmp/cargo-install.X8OUPaXeZE4M`

Caused by:
  no matching package named `ring` found (required by `multihash`)
location searched: registry https://github.com/rust-lang/crates.io-index
version required: ~0.6.2
versions found: 0.9.7, 0.9.6, 0.9.5, ...

Tue  6 Jun 21:32:27 BST 2017

and /tmp/cargo-install.X8OUPaXeZE4M is empty.

In my second attempt, as a preparation, I had wiped everything before:

rm .cargo -rf
curl https://sh.rustup.rs -sSf | sh
source $HOME/.cargo/env

rustc --version
    rustc 1.17.0 (56124baa9 2017-04-24)

rustc --version
    cargo 0.18.0 (fe7b0cdcf 2017-04-24)
Z7-duplicate 馃枿

All 15 comments

The updated cid package PR has been made 21 days ago, but it wasn't released yet.
https://github.com/ipld/rust-cid/pull/6
If it is not released today I'll use the github version instead.

What if instead of the failing

cargo install --git https://github.com/paritytech/parity.git

I'd simply go back to a (presumably working) v1.6.7? Let's see how this goes:

date; cargo install --git https://github.com/paritytech/parity --tag v1.6.7 parity; date

The problem is that ring-0.6 has been removed from crates.io registry. So any version won't work.

You @5chdn closing this issue - means that the problem is completely resolved?

I am now waiting almost 2 hours already - or does parity always need that long?

rm .cargo -rf
curl https://sh.rustup.rs -sSf | sh
1
source $HOME/.cargo/env

date; cargo install --git https://github.com/paritytech/parity parity; date

Wed  7 Jun 10:57:47 BST 2017

    Updating git repository `https://github.com/paritytech/parity`
  Installing parity v1.7.0 (https://github.com/paritytech/parity#19f01194)
    Updating registry `https://github.com/rust-lang/crates.io-index`
    Updating git repository `https://github.com/paritytech/rust-ctrlc.git`
    Updating git repository `https://github.com/paritytech/jsonrpc.git`
    Updating git repository `https://github.com/paritytech/rust-rocksdb`
    Updating git repository `https://github.com/paritytech/rust-secp256k1`
    Updating git repository `https://github.com/paritytech/bn`
    Updating git repository `https://github.com/paritytech/hyper`
    Updating git repository `https://github.com/paritytech/nanomsg.rs.git`
    Updating git repository `https://github.com/tailhook/rotor`
    Updating git repository `https://github.com/tomusdrw/ws-rs`
    Updating git repository `https://github.com/nikvolf/parity-tokio-ipc`
    Updating git repository `https://github.com/alexcrichton/mio-named-pipes`
    Updating git repository `https://github.com/nikvolf/tokio-named-pipes`
    Updating git repository `https://github.com/tomusdrw/tokio-proto`
    Updating git repository `https://github.com/tomusdrw/tokio-minihttp`
    Updating git repository `https://github.com/paritytech/js-precompiled.git`
    Updating git repository `https://github.com/paritytech/libusb-rs`
    Updating git repository `https://github.com/paritytech/hidapi-rs`
    Updating git repository `https://github.com/paritytech/libusb-sys`

stuck there.

3 hours now.

I get the impression this is perhaps not yet fixed ...?

It looks it's trying to fetch all the dependencies. What internet connection do you have?

What internet connection do you have?

88.92 Mbps, just measured for you.
87.04 Mbps upload.

That's weird what kind of CPU / disk?
The process looks normal, compiling Parity from scratch should not take longer than 20 minutes on a decent machine when all dependencies are already fetched.

I just realized that now you might be experiencing the issues linked by @5chdn https://github.com/rust-lang/cargo/issues/4108

Yes I closed it because it's tracked in the two other tickets above and a fix is available in #5785. This does not mean I do not endorse this discussion.

CPU

i5-6500 CPU @ 3.20GHz

disk?

SSD

should not take longer than 20 minutes

The last attempt is already 6 hours old now. And still running.

you might be experiencing the issues linked by @5chdn rust-lang/cargo#4108

"alexcrichton closed this 8 days ago"

when all dependencies are already fetched.

how to perhaps do that manually ?

and a fix is available in #5785

Great. How exactly can I use that fix ?

thanks.

@alexcrichton said here:

"ah yeah unfortunately that's this issue :("

you might be experiencing the issues linked by @5chdn rust-lang/cargo#4108

"alexcrichton closed this 8 days ago"

This one is the correct ticket https://github.com/rust-lang/cargo/issues/4066

Great. How exactly can I use that fix ?

Try to build latest master or beta:

cargo install --git https://github.com/paritytech/parity parity
Was this page helpful?
0 / 5 - 0 ratings

Related issues

jurijbajzelj picture jurijbajzelj  路  3Comments

jacogr picture jacogr  路  4Comments

bryaan picture bryaan  路  3Comments

m-thomson picture m-thomson  路  3Comments

Michael2008S picture Michael2008S  路  3Comments