Closed kpcyrd closed 5 years ago
hey!
the latest release ships a Cargo.lock that still points to 0.4.0. cargo probably updates this automatically the next time after cargo is invoked, but the current latest release can't be built with --locked due to this.
This is commonly done in archlinux.
hey!
the latest release ships a Cargo.lock that still points to 0.4.0. cargo probably updates this automatically the next time after cargo is invoked, but the current latest release can't be built with --locked due to this.
This is commonly done in archlinux.