--- Log opened Mon Nov 09 00:00:11 2020 01:13 -!- zoe_ [uid464843@gateway/web/irccloud.com/x-iartyncocatqpnju] has joined #lnp-bp 06:13 < dieeasy> hi, I noticed that package lnpbp appears twice in Cargo.lock (in master, commit 6d6611f), once with version 0.2.0-beta.2 from crates.io and the other with version 0.2.0-beta.3 (with no "source"), is this correct? I suspect this is causing some issues 08:55 < dieeasy> sorry, just noticed I didn't mention the project name, this happens in rust-lnpbp 14:33 -!- zoe_ [uid464843@gateway/web/irccloud.com/x-iartyncocatqpnju] has quit [Quit: Connection closed for inactivity] 15:03 -!- danger73 [925aea13@19.234.90.146.dyn.plus.net] has joined #lnp-bp 15:04 -!- danger73 [925aea13@19.234.90.146.dyn.plus.net] has left #lnp-bp [] 23:57 < dr_orlovsky> > hi, I noticed that package lnpbp appears twice in Cargo.lock (in master, commit 6d6611f), once with version 0.2.0-beta.2 from crates.io and the other with version 0.2.0-beta.3 (with no "source"), is this correct? I suspect this is causing some issues 23:59 < dr_orlovsky> This is a normal thing. First, Cargo.lock is managed internally by cargo. AFAIR it just lists all dependencies, so somewhere some of the crates was using other version of the lib. You can run cargo update any time and see whether it changes anything. But have to say never looked into Cargo.lock manually and never had a problems which can't be solved by just removing it --- Log closed Tue Nov 10 00:00:12 2020