If you use pants <= 0.0.79 you can work around install issues by either upgrading pants to 0.0.80 or beyond where the lockfile dependency is removed, or you can pin the pbr dependency on lockfile's behalf. If you use the standard pants bootstrap script [6] this edit accomplished the goal:
diff --git a/pants b/pants
index 0ce4114..b974351 100755
--- a/pants
+++ b/pants
@@ -83,7 +83,7 @@ function bootstrap_pants {
staging_dir=$(tempdir "${PANTS_BOOTSTRAP}") && \
"${PYTHON}" "${venv_path}/virtualenv.py" "${staging_dir}/install" && \
source "${staging_dir}/install/bin/activate" && \
- pip install "${pants_requirement}" && \
+ pip install "${pants_requirement}" pbr==1.9.0 && \
ln -s "${staging_dir}/install" "${staging_dir}/${pants_version}" && \
mv "${staging_dir}/${pants_version}" "${PANTS_BOOTSTRAP}/${pants_version}"
) 1>&2
Here we ask pip to install both pants and pbr at version 1.9.0 - the version before the breaking 4/14 release.
Please speak up if you are hitting the issue and are unable to apply the above workaround due to a custom pants setup procedure, we may be able to help.