Hello community,
here is the log from the commit of package bazel for openSUSE:Factory checked in at 2019-04-11 12:18:04
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/bazel (Old)
and /work/SRC/openSUSE:Factory/.bazel.new.27019 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "bazel"
Thu Apr 11 12:18:04 2019 rev:6 rq:693016 version:0.24.1
Changes:
--------
--- /work/SRC/openSUSE:Factory/bazel/bazel.changes 2019-03-20 13:19:58.581333866 +0100
+++ /work/SRC/openSUSE:Factory/.bazel.new.27019/bazel.changes 2019-04-11 12:18:16.448964916 +0200
@@ -1,0 +2,82 @@
+Tue Apr 9 20:17:30 UTC 2019 - Matthias Eliasson
+
+- Update to version 0.24.1
+ Cherrypicks:
+ * Wrap StatusRuntimeExceptions from GrpcRemoteCache
+- Changes in 0.24.0
+ Incompatible changes:
+ * Added --incompatible_py3_is_default to test switching the default
+ Python version to PY3 for py_binary/py_test targets that do not
+ specify a version.
+ * //tools/cmd_line_differ has been renamed to //tools/aquery_differ
+ & can now compare (in addition to command lines) inputs of
+ actions given 2 aquery results.
+ * java_(mutable_|)proto_library: removed strict_deps attribute.
+ * The flag --incompatible_list_based_execution_strategy_selection
+ was added and is used to ease the migration to the new style of
+ specifying
+ execution strategy selection and fallback behavior.
+ * Added --incompatible_py2_outputs_are_suffixed, for switching the
+ bazel-bin symlink to point to Python 3 outputs instead of Python
+ 2 outputs.
+ New features:
+ * Make actions.args() object chainable.
+ * Added --incompatible_windows_style_arg_escaping flag: enables
+ correct subprocess argument escaping on Windows. (No-op on other
+ platforms.)
+ * Added --incompatible_windows_escape_jvm_flags flag: enables
+ correct java_binary.jvm_flags and java_test.jvm_flags
+ tokenization and escaping on Windows. (No-op on other platforms.)
+ Important changes:
+ * Allow running aquery against the current state of Skyframe
+ * Added support for the "navigation" resource directory to Android
+ resource processing in Bazel. This is used by the Navigation
+ Architecture Component.
+ * --incompatible_disable_runtimes_filegroups was flipped
+ * Incompatible flag --incompatible_linkopts_in_user_link_flags
+ has been flipped
+ * Incompatible flag --incompatible_dont_emit_static_libgcc has
+ been flipped
+ * --incompatible_disallow_filetype is enabled by default.
+ * Fixed issue where exceptions and stacktraces were silently
+ swallowed in the Android resource processing pipeline.
+ * --incompatible_disable_expand_if_all_available_in_flag_set has
+ been flipped
+ * --incompatible_disallow_dict_plus is enabled by default
+ * Adds --incompatible_disable_objc_library_resources to disable
+ resource attributes in objc_library. Please migrate these
+ attributes to data instead.
+ * --incompatible_disallow_old_style_args_add is enabled by default.
+ * Using the native module in BUILD files is deprecated. It will
+ be forbidden with --incompatible_disallow_native_in_build_file.
+ * (Python rules) PyRuntimeInfo is exposed to Starlark, making it
+ possible for Starlark rules to depend on or imitate py_runtime.
+ The files attribute of py_runtime is no longer mandatory.
+ * incompatible_use_toolchain_providers_in_java_common: pass
+ JavaToolchainInfo and JavaRuntimeInfo providers to java_common
+ APIs instead of configured
+ targets
+ * is_using_fission crosstool variable is now exposed in all compile
+ actions when fission is active (it used to be exposed only for
+ linking actions).
+ * incompatible_use_toolchain_providers_in_java_common: pass
+ JavaToolchainInfo and JavaRuntimeInfo providers to java_common
+ APIs instead of configured
+ targets
+ * py_runtime gains a python_version attribute for specifying
+ whether it represents a Python 2 or 3 interpreter.
+ * --incompatible_java_coverage is enabled by default.
+ * Starlark rules can safely declare attributes named "licenses"
+ * When using
+ --incompatible_list_based_execution_strategy_selection, Bazel
+ will use remote execution by default (if you specify
+ --remote_executor), otherwise persistent workers (if the action
+ supports it), otherwise sandboxed local execution (if the action
+ and platform supports it) and at last unsandboxed local
+ execution. The flags --spawn_strategy and --strategy continue to
+ work as before - this only sets new defaults for the case where
+ you don't specify these flags.
+ * Set default value of --incompatible_remap_main_repo to true.
+ * Set default value of --incompatible_remap_main_repo to true.
+
+-------------------------------------------------------------------
Old:
----
bazel-0.22.0-dist.zip
bazel-0.22.0-dist.zip.sig
New:
----
bazel-0.24.1-dist.zip
bazel-0.24.1-dist.zip.sig
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ bazel.spec ++++++
--- /var/tmp/diff_new_pack.BR89I8/_old 2019-04-11 12:18:20.176966798 +0200
+++ /var/tmp/diff_new_pack.BR89I8/_new 2019-04-11 12:18:20.184966802 +0200
@@ -18,7 +18,7 @@
%define bashcompdir %(pkg-config --variable=completionsdir bash-completion 2>/dev/null)
Name: bazel
-Version: 0.22.0
+Version: 0.24.1
Release: 0
Summary: Tool for the automation of building and testing of software
License: Apache-2.0
