Update for cargo 1.80.0+

[bleetube]

Building with cargo 1.82.0 throws an error about an API change in Rust. The error message suggests running cargo update. I'm going to give that a shot.

nix-shell -p cargo --run "cargo version"
cargo 1.82.0 (8f40fc59f 2024-08-21)
nix-shell -p cargo --run "cargo build"
    Updating git repository `https://github.com/Blockstream/greenlight`
    Updating crates.io index
...
   Compiling bitcoin-consensus-derive v0.1.0
error[E0282]: type annotations needed for `Box<_>`
  --> /home/blee/.cargo/registry/src/index.crates.io-6f17d22bba15001f/time-0.3.34/src/format_description/parse/mod.rs:83:9
   |
83 |     let items = format_items
   |         ^^^^^
...
86 |     Ok(items.into())
   |              ---- type must be known at this point
   |
   = note: this is an inference error on crate `time` caused by an API change in Rust 1.80.0; update `time` to version `>=0.3.35` by calling `cargo update`

   Compiling secp256k1-sys v0.8.1
   Compiling indexmap v1.9.3
   Compiling prost-build v0.11.9
   Compiling cpufeatures v0.2.12
   Compiling termcolor v1.4.1
   Compiling humantime v2.1.0
   Compiling bitcoin-private v0.1.0
   Compiling chunked-buffer v0.2.0
   Compiling tinyvec_macros v0.1.1
   Compiling tinyvec v1.6.0
For more information about this error, try `rustc --explain E0282`.
error: could not compile `time` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...

[rolznz]

Hi, which project do you use the bindings for?

Alby Hub no longer supports Greenlight so we unfortunately won't be able to maintain this project going forward.

[bleetube]

Oh, thank you! I opened this because I'm trying to build an albyhub package, which still includes this library pre-compiled via the glalby-go binding:

grep glalby-go hub/go.mod
        github.com/getAlby/glalby-go v0.0.0-20240621192717-95673c864d59

I'll assume its going to be removed soon and attempt to workaround building it in the meantime.

[rolznz]

@bleetube sorry you encountered this issue. I will try to have it removed as part of 1.16 release. Please let me know if you are blocked.