Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package jujutsu for openSUSE:Factory checked 
in at 2024-06-09 20:22:25
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/jujutsu (Old)
 and      /work/SRC/openSUSE:Factory/.jujutsu.new.19518 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "jujutsu"

Sun Jun  9 20:22:25 2024 rev:9 rq:1179395 version:0.18.0

Changes:
--------
--- /work/SRC/openSUSE:Factory/jujutsu/jujutsu.changes  2024-05-09 
17:28:35.395240027 +0200
+++ /work/SRC/openSUSE:Factory/.jujutsu.new.19518/jujutsu.changes       
2024-06-09 20:24:51.183524010 +0200
@@ -1,0 +2,81 @@
+Fri Jun  7 20:02:25 UTC 2024 - Johannes Kastl 
<opensuse_buildserv...@ojkastl.de>
+
+- update to 0.18.0:
+  * Breaking changes
+    - Dropped support for ui.default-revset config (replaced by
+      revsets.log in 0.8.0).
+    - The commit_summary_no_branches template is superseded by
+      templates.branch_list.
+    - jj split will now refuse to split an empty commit.
+    - jj config list now uses multi-line strings and single-quoted
+      strings in the output when appropriate.
+    - jj config get/list/set now parse name argument as TOML key.
+      Quote meta characters as needed.  Example: jj config get
+      "revset-aliases.'trunk()'"
+    - When updating the working copy away from an empty and
+      undescribed commit, it is now abandoned even if it is a merge
+      commit.
+    - If a new working-copy commit is created because the old one
+      was abandoned, and the old commit was merge, then the new
+      commit will now also be.  #2859
+    - jj new's --insert-before/--insert-after options must now be
+      set for each commit the new commit will be inserted
+      before/after. Previously, those options were global flags and
+      specifying them once would insert the new commit before/
+      after all the specified commits.
+  * Deprecations
+    - Attempting to alias a built-in command now gives a warning, rather than 
being
+      silently ignored.
+  * New features
+    - jj branch list/tag list now accept -T/--template option. The
+      tag list prints commit summary along with the tag name by
+      default.
+    - Conflict markers now include an explanation of what each part
+      of the conflict represents.
+    - ui.color = "debug" prints active labels alongside the regular
+      colored output.
+    - jj branch track now show conflicts if there are some.
+    - A new revset reachable(srcs, domain) will return all commits
+      that are reachable from srcs within domain.
+    - There are now prebuilt binaries for
+      aarch64-linux-unknown-musl.  Note, these are cross compiled
+      and currently untested.  We plan on providing fully tested
+      builds later once our CI system allows it.
+    - Added new revsets mutable() and immutable().
+    - Upgraded scm-record from v0.2.0 to v0.3.0. See release notes
+      at https://github.com/arxanas/scm-record/releases/tag/v0.3.0
+    - New command jj fix that can be configured to update commits
+      by running code formatters (or similar tools) on changed
+      files. The configuration schema and flags are minimal for
+      now, with a number of improvements planned (for example,
+      #3800 and #3801).
+    - jj new's --insert-before and --insert-after options can now
+      be used simultaneously.
+    - jj git push now can push commits with empty descriptions with
+      the --allow-empty-description flag
+  * Fixed bugs
+    - Previously, jj git push only made sure that the branch is in
+      the expected location on the remote server when pushing a
+      branch forward (as opposed to sideways or backwards). Now, jj
+      git push makes a safety check in all cases and fails whenever
+      jj git fetch would have introduced a conflict.
+      In other words, previously branches that moved sideways or
+      backward were pushed similarly to Git's git push --force; now
+      they have protections similar to git push --force-with-lease
+      (though not identical to it, to match the behavior of jj git
+      fetch). Note also that because of the way jj git fetch works,
+      jj does not suffer from the same problems as Git's git push
+      --force-with-lease in situations when git fetch is run in the
+      background.
+    - When the working copy commit becomes immutable, a new one is
+      automatically created on top of it to avoid letting the user
+      edit the immutable one.
+    - jj config list now properly escapes TOML keys (#1322).
+    - Files with conflicts are now checked out as executable if all
+      sides of the conflict are executable.
+    - The progress bar (visible when using e.g. jj git clone)
+      clears the remainder of the cursor row after drawing rather
+      than clearing the entire row before drawing, eliminating the
+      "flicker" effect seen on some terminals.
+
+-------------------------------------------------------------------

Old:
----
  jj-0.17.1.obscpio

New:
----
  jj-0.18.0.obscpio

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ jujutsu.spec ++++++
--- /var/tmp/diff_new_pack.BSF9cq/_old  2024-06-09 20:24:52.327565293 +0200
+++ /var/tmp/diff_new_pack.BSF9cq/_new  2024-06-09 20:24:52.331565436 +0200
@@ -19,7 +19,7 @@
 %define binary_name jj
 
 Name:           jujutsu
-Version:        0.17.1
+Version:        0.18.0
 Release:        0
 Summary:        Git-compatible DVCS that is both simple and powerful
 License:        MIT
@@ -56,6 +56,7 @@
 install -m 0755 
%{_builddir}/%{binary_name}-%{version}/target/release/%{binary_name} 
%{buildroot}%{_bindir}/%{binary_name}
 
 %check
+rm -rf tests/contest/
 %{cargo_test}
 
 %files

++++++ _service ++++++
--- /var/tmp/diff_new_pack.BSF9cq/_old  2024-06-09 20:24:52.367566736 +0200
+++ /var/tmp/diff_new_pack.BSF9cq/_new  2024-06-09 20:24:52.371566880 +0200
@@ -4,7 +4,7 @@
     <param name="scm">git</param>
     <param name="exclude">.git</param>
     <param name="versionformat">@PARENT_TAG@</param>
-    <param name="revision">v0.17.1</param>
+    <param name="revision">v0.18.0</param>
     <param name="changesgenerate">disable</param>
     <param name="versionrewrite-pattern">v(.*)</param>
   </service>

++++++ jj-0.17.1.obscpio -> jj-0.18.0.obscpio ++++++
++++ 30206 lines of diff (skipped)

++++++ jj.obsinfo ++++++
--- /var/tmp/diff_new_pack.BSF9cq/_old  2024-06-09 20:24:52.743580304 +0200
+++ /var/tmp/diff_new_pack.BSF9cq/_new  2024-06-09 20:24:52.747580448 +0200
@@ -1,5 +1,5 @@
 name: jj
-version: 0.17.1
-mtime: 1715096394
-commit: e1d8705546d3971fef23bc6a4a7589283e5e0717
+version: 0.18.0
+mtime: 1717670815
+commit: 9fb5307b7886e390c02817af7c31b403f0279144
 

++++++ vendor.tar.zst ++++++
/work/SRC/openSUSE:Factory/jujutsu/vendor.tar.zst 
/work/SRC/openSUSE:Factory/.jujutsu.new.19518/vendor.tar.zst differ: char 7, 
line 1

Reply via email to