just last night there was a fix for file_util not having a lockfile, for example

which would prevent the issue moving forward, but not help with older shas

Is there some hack around?

What is the nature of the problem, in fact?

Surely there must be some state I can nuke

the nature of the problem is that in the absence of a lockfile, versions float

so new versions of transitive dependencies are being resolved, because they exist

it's the absence of state, rather than its existence =/

(i think. what's the latest error?)

it's likely possible to specify more versions in

Cargo.toml

... i might be able to try that later today

and push a branch with some edits

@happy-kitchen-89482: ^

we're trying to run a hotfix internally to begin the pantsd beta, so we've all been a bit distracted

gotcha

something from https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#overriding-dependencies

but yea, i can take a look tonight.

Thanks - it’s just not great if we can’t build a commit from 60 days ago…

yes. understood. it was a bug.

filed https://github.com/pantsbuild/pants/issues/5285 for strategy discussion on interruptable execution - lmk if anyone has any thoughts there.

got the following for building engine on wheezy:

@wide-energy-11069 uploaded a file: Untitled

related to boringssl

why wheezy?

(for the record: travis is building binaries on centos6 now, as of about halfway down https://github.com/pantsbuild/pants/issues/4896)

@witty-crayon-22786 internal release script

mm.

currently nuking everything and trying again

no dice. but maybe the flags are mixed up, given

cc1: all warnings being treated as errors

@happy-kitchen-89482: looks like the grpc thing you saw was due to a floating grpc compiler (since fixed by one of Daniel's patches). can apply the following to get it compiling:

diff --git a/build-support/bin/native/bootstrap.sh b/build-support/bin/native/bootstrap.sh
index aabe01a..f732d46 100644
--- a/build-support/bin/native/bootstrap.sh
+++ b/build-support/bin/native/bootstrap.sh
@@ -93,8 +93,11 @@ function ensure_native_build_prerequisites() {
   if [[ ! -x "${CARGO_HOME}/bin/protoc-gen-rust" ]]; then
     "${CARGO_HOME}/bin/cargo" install protobuf >&2
   fi
-  if [[ ! -x "${CARGO_HOME}/bin/grpc_rust_plugin" ]]; then
-    "${CARGO_HOME}/bin/cargo" install grpcio-compiler >&2
+  if [[ ! -x "${CARGO_HOME}/bin/grpc_rust_plugin" ]] || ! grep '^"grpcio-compiler .*2acabdbff71e77a14b95b0b30c6d7de516355df7' "${CARGO_HOME}/.crates.toml" >/dev/null 2>/dev/null; then
+    # Force install of a version we know is compatible with the version of grpc we use.
+    # There hasn't been a release since the changes we depend on (<https://github.com/pingcap/grpc-rs/pull/101>)
+    # so we need to manually mess with versions here.
+    "${CARGO_HOME}/bin/cargo" install --force --git=<https://github.com/illicitonion/grpc-rs> --rev=2acabdbff71e77a14b95b0b30c6d7de516355df7 grpcio-compiler >&2
   fi
   if [[ ! -x "${CARGO_HOME}/bin/rustfmt" ]]; then
     "${CARGO_HOME}/bin/cargo" install rustfmt >&2

That didn’t solve the problem. I’ve given up and closed that issue, since it no longer reproduces.