--- Log opened Mon Sep 28 00:00:31 2020
00:28 -!- jonatack [~jon@37.167.90.115] has quit [Ping timeout: 265 seconds]
00:39 -!- jonatack [~jon@37.167.90.115] has joined #rust-bitcoin
00:51 -!- jonatack [~jon@37.167.90.115] has quit [Quit: jonatack]
00:51 -!- jonatack [~jon@213.152.180.5] has joined #rust-bitcoin
02:17 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection]
03:20 -!- Jakayla45Kertzma [~Jakayla45@static.57.1.216.95.clients.your-server.de] has joined #rust-bitcoin
03:47 -!- jonatack [~jon@213.152.180.5] has quit [Ping timeout: 240 seconds]
04:17 -!- jonatack [~jon@37.167.111.11] has joined #rust-bitcoin
04:33 -!- jonatack [~jon@37.167.111.11] has quit [Ping timeout: 256 seconds]
05:23 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #rust-bitcoin
06:36 < stevenroose> I notice the secp256k1-sys MSRV was bumped to 1.29 but it doesn't seem we use any of the 1.29 features.. So I don't really see why that wsa done.
06:37 < stevenroose> I can still build it with 1.22 perfectly (after just fixing the cc dependency)
06:37 < stevenroose> elichai2: I see it was done as part of a general effort to up the MSRV of rust-bitcoin ot 1.29? in https://github.com/rust-bitcoin/rust-bitcoin/issues/338
06:42 < elichai2> Andytoshi wanted to ease the users on the upgrade, so the bump was only a changelog saying the new MSRV, nothing new really, later versions will now actually use 1.29 features
06:44 < andytoshi> stevenroose: we had to bump the MSRV before actually using any features
06:45 < andytoshi> for rust-secp i believe the new features we want are related to alignment etc., but i haven't taken a look at that yet
06:46 < stevenroose> it seems that for me building with 1.29 doesn't work without restricting the `cc` dependency: https://github.com/rust-bitcoin/rust-secp256k1/pull/240
06:53 < stevenroose> I'm confused though why it breaks only now in 1.0.60 while the edition= field has been there since 1.0.42
06:53 < andytoshi> the workaround is in the README
06:53 < andytoshi> of rust-secp
06:53 < andytoshi> we can't fix cc
06:53 < andytoshi> because that will break the build for people who depend on higher versions
06:57 < stevenroose> pfff
06:58 < andytoshi> yeah. such is life in the cargo ecosystem :/
06:59 < stevenroose> Let's start a crowdfunder for those Rust devs that just got fired from Mozilla and fund them to build a fork of Cargo that enforces MSRV (somehow) :D
07:00 < stevenroose> uh, so ok so Riccardo will then have to do the same cargo update thing for elements, I suppose
07:01 < andytoshi> if he's using rust 1.29
07:01 < andytoshi> then yeha
07:01 < andytoshi> ah i guess we haven't specified a MSRV or written a real readme for rust-elements. lol
07:02 < andytoshi> oh i see he comments about this in https://github.com/ElementsProject/rust-elements/pull/56
07:02 < andytoshi> but it's specified in the README for rust-bitcoin https://github.com/rust-bitcoin/rust-bitcoin#minimum-supported-rust-version-msrv
09:28 < elichai2> stevenroose: there's already an rfc on MSRV aware cargo. But no one really cares about this
09:57 < stevenroose> I thought it would be really great to have some kind of versions.rs website that reports compatibility of crates with different cargo versions
17:48 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 240 seconds]
17:48 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #rust-bitcoin
23:17 -!- shesek [~shesek@164.90.217.137] has joined #rust-bitcoin
23:17 -!- shesek [~shesek@164.90.217.137] has quit [Changing host]
23:17 -!- shesek [~shesek@unaffiliated/shesek] has joined #rust-bitcoin
23:57 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 260 seconds]
--- Log closed Tue Sep 29 00:00:32 2020