You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The crate bls_dkg mentions in its changelog concerns about multiple versions of blsttc and rand used together.
I might be ready too much into that (quite possible: I am new to Rust!) but if generally risky to mix multiple instances of blsttc and rust into a project then this seems to currently be the case with safe_network, as sn_api depends on newer releases via sn_dbc.
Even if not an issue technically, please consider anyway migrating to the newer rand v0.8: I am working on packaging safe_network officially for Debian, which requires packaging each and every dependency - and rand v0.8 is currently packaged but v0.7 is not, and I will expect Debian maintainers of the v0.8 crate to be hesitant to introducing the v0.7 crate, preferring instead to try coerce projects to use the newer and likely better maintained v0.8.
The text was updated successfully, but these errors were encountered:
yeah, I am not a Rust coder (only look at it for the purpose of integrating with the Debian distribution) but do sense some potential headaches in the area of rand versions...
I wish you the best of luck with the upgrade task :-)
The crate
bls_dkg
mentions in its changelog concerns about multiple versions ofblsttc
andrand
used together.I might be ready too much into that (quite possible: I am new to Rust!) but if generally risky to mix multiple instances of
blsttc
andrust
into a project then this seems to currently be the case with safe_network, assn_api
depends on newer releases viasn_dbc
.Even if not an issue technically, please consider anyway migrating to the newer rand v0.8: I am working on packaging safe_network officially for Debian, which requires packaging each and every dependency - and
rand
v0.8 is currently packaged but v0.7 is not, and I will expect Debian maintainers of the v0.8 crate to be hesitant to introducing the v0.7 crate, preferring instead to try coerce projects to use the newer and likely better maintained v0.8.The text was updated successfully, but these errors were encountered: