Closed getong closed 7 months ago
I don't think we want to bump the MSRV on this crate to 1.67.0. We will however need to find another way forward, e.g., by carefully pinning the respective offending dependency in CI (I think in this case it would be safe as it's just a downstream dependency of our electrsd
test dependency I believe), or by introducing a script to download and run bitcoind
/electrs
as we did in LDK.
I don't think we want to bump the MSRV on this crate to 1.67.0. We will however need to find another way forward, e.g., by carefully pinning the respective offending dependency in CI (I think in this case it would be safe as it's just a downstream dependency of our
electrsd
test dependency I believe), or by introducing a script to download and runbitcoind
/electrs
as we did in LDK.
I am afraid not.
electrum-client use bitcoin 0.31 from version 0.19. electrsd use electrum-client 0.19 from 0.27, so electrsd cannot be downstream here.
I don't think we want to bump the MSRV on this crate to 1.67.0. We will however need to find another way forward, e.g., by carefully pinning the respective offending dependency in CI (I think in this case it would be safe as it's just a downstream dependency of our
electrsd
test dependency I believe), or by introducing a script to download and runbitcoind
/electrs
as we did in LDK.I am afraid not.
electrum-client use bitcoin 0.31 from version 0.19. electrsd use electrum-client 0.19 from 0.27, so electrsd cannot be downstream here.
I think there is a misunderstanding here: it's true we can't downgrade the electrsd
dependency, but we can pin the dependencies downstream from it that do not meet the MSRV.
I revert the code, but this error seems that it might be jobserver, I make a issue of it. rust-lang/jobserver-rs#69
Hey mate, I pushed up #79 to do the upgrade which is getting past CI now.
This is a fix of #60 , which update rust to 1.67. It fix the ci error.