On Mon, Apr 9, 2018 at 10:32 PM, <twisniew...@mozilla.com> wrote:
> On Monday, April 9, 2018 at 11:39:35 AM UTC-4, Henri Sivonen wrote:
>> How do I waive .cargo-checksum.json checking for a crate?
> In bug 1449613 (part 12) I just hand-edited the .cargo-checksum.json in
> question, and updated the sha256 values for the modified files. That was
> enough to get try runs going (though the debug builds do show related
> failures, they still built and ran my tests).
This is what I've done, but it shouldn't have to be like this.
On Mon, Apr 9, 2018 at 8:48 PM, Andreas Tolfsen <a...@sny.no> wrote:
> I don’t know the exact answer to your question, but it might be
> possible to temporarily depend on the crate by a its path?
> There are a couple of examples of this in
> Remember to run "cargo update -p <crate name>".
This seems more complicated than editing the crate in place and
manually editing the sha256 values.
What I'm looking for is a simple way to skip the sha256 editing.
dev-platform mailing list