To be clear, this doesn't affect the binaries we produce. We build using the in-tree versions of all the crates. The published versions are for the benefit of people who build from the GitHub export of the source code. I *think* what's going on here is that during a previous release we neglected to upload mozdevice, so building from GitHub didn't work. Then I assume this other person published it. But I don't know how to verify the version of the code in the crate matches what we published. It seems they also published the marionette crate, which I think should be unnecessary, and the geckodriver crate which we intentionally didn't because we didn't intend to use `cargo install` as a distribution mechanism. It sounds like in the first instance we can try to contact the person and hope to resolve the situation that way.
Bug 1656157 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
To be clear, this doesn't affect the binaries we produce. We build using the in-tree versions of all the crates. The published versions are for the benefit of people who build from the GitHub export of the source code. I *think* what's going on here is that during a previous release we neglected to upload mozdevice, so building from GitHub didn't work. Then I assume this other person published it. But I don't know how to verify the version of the code in the crate matches our previous release. It seems they also published the marionette crate, which I think should be unnecessary, and the geckodriver crate which we intentionally didn't because we didn't intend to use `cargo install` as a distribution mechanism. It sounds like in the first instance we can try to contact the person and hope to resolve the situation that way.