Hello community,

here is the log from the commit of package libostree for openSUSE:Factory 
checked in at 2018-05-07 14:50:37
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/libostree (Old)
 and      /work/SRC/openSUSE:Factory/.libostree.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "libostree"

Mon May  7 14:50:37 2018 rev:10 rq:603000 version:2018.4

Changes:
--------
--- /work/SRC/openSUSE:Factory/libostree/libostree.changes      2018-04-07 
20:54:19.384327811 +0200
+++ /work/SRC/openSUSE:Factory/.libostree.new/libostree.changes 2018-05-07 
14:50:39.167705003 +0200
@@ -1,0 +2,66 @@
+Wed May 02 05:42:01 UTC 2018 - [email protected]
+
+- Update to version 2018.4:
+  + A quick turnaround after 2018.3 to include one main PR:
+    gh#ostreedev/ostree#1508.
+  + "switchroot: Ensure /run/ostree-booted is created even without
+    initramfs".
+  + This fixes ostree when booting without an initramfs. Thanks to
+    @akiernan for the bug report and helping review the fix! I'm
+    working on enhancing the test suite, which will help in adding
+    some coverage here.
+- Changes from version 2018.3:
+  + Keeping up with our ~monthly cadence. A variety of contributors
+    here again, it's great to see! There's two notable features,
+    and a variety of non-critical bugfixes.
+  + On the features side we have:
+    - sysroot: Add concept of deployment "pinning".
+    - ostree: introduce PAYLOAD_LINK object type.
+    - lib/fetcher: Allow clients to append to User-Agent.
+  + By default libostree prunes older deployments; the pinning
+    feature allows you to explicitly retain them until unpinned.
+    This is useful for major version updates.
+  + The PAYLOAD_LINK functionality allows libostree to do
+    content-based deduplication. Previously, if e.g. a file changes
+    in metadata (mode, owner, xattrs such as SELinux labels), we
+    can't make a plain Unix hardlink, and hence by default end up
+    with a new copy on disk. However, the Linux kernel has
+    standardized "reflinks" and some filesystems support them,
+    including modern versions of XFS. When reflinks are available,
+    this functionality causes libostree to compute a content-only
+    payload, and when importing an object, if it matches in content
+    with an existing object, to use reflinks to deduplicate, while
+    using different inodes.
+  + Finally, the HTTP User-Agent API is intended for higher level
+    tools linking to libostree where one wants to expose the app
+    version as well.
+  + Beyond that, as mentioned above we have a variety of
+    non-critical fixes such as memory leaks, test suite
+    improvements, correctly printing the "would be pruned" size
+    when using prune --no-prune, etc.
+- Changes from version 2018.2:
+  + We're keeping up with the approximately-monthly release cycle.
+    There's mostly a collection of smaller fixes here, with some
+    enhancements. I'm biased but my personal favorite is
+    gh#ostreedev/ostree#1438 since it makes the output of findmnt
+    rather significantly nicer on this workstation where I have
+    container tooling creating sub-mounts in /var that are no
+    longer replicated in /sysroot.
+  + For the embedded space, gh#ostreedev/ostree#1411 for devicetree
+    support is likely interesting, and is related to a discussion
+    on the mailing list:
+    https://mail.gnome.org/archives/ostree-list/2018-February/msg00001.html
+  + Jonathan's PR gh#ostreedev/ostree#1441 to add callback
+    filtering to checkout was necessary for us to re-implement some
+    hairy logic from librpm around "file coloring"; see
+    projectatomic/rpm-ostree#1227 We're getting quite far along now
+    in having rpm-ostree be a truly hybrid system, supporting the
+    existing RPM ecosystem.
+  + Marcus definitely wins the "lines changed" count this cycle by
+    adding SPDX-License-Identifier to all of the C source files
+    (gh#ostreedev/ostree#1439). This happened because we relicensed
+    the documentation to dual CC BY-SA and GFDL in
+    gh#ostreedev/ostree#1432 to enable a Wikipedia page which I
+    just noticed exists now!
+
+-------------------------------------------------------------------

Old:
----
  libostree-2018.1.tar.xz

New:
----
  libostree-2018.4.tar.xz

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

Other differences:
------------------
++++++ libostree.spec ++++++
--- /var/tmp/diff_new_pack.5RGT2y/_old  2018-05-07 14:50:40.331668684 +0200
+++ /var/tmp/diff_new_pack.5RGT2y/_new  2018-05-07 14:50:40.343668309 +0200
@@ -17,7 +17,7 @@
 
 
 Name:           libostree
-Version:        2018.1
+Version:        2018.4
 Release:        0
 Summary:        Git for operating system binaries
 License:        LGPL-2.0-or-later

++++++ _service ++++++
--- /var/tmp/diff_new_pack.5RGT2y/_old  2018-05-07 14:50:40.411666187 +0200
+++ /var/tmp/diff_new_pack.5RGT2y/_new  2018-05-07 14:50:40.411666187 +0200
@@ -6,7 +6,7 @@
     <param name="versionrewrite-pattern">v(.*)</param>
     <param name="filename">libostree</param>
     <param name="changesgenerate">enable</param>
-    <param name="revision">refs/tags/v2018.1</param>
+    <param name="revision">refs/tags/v2018.4</param>
   </service>
   <service name="recompress" mode="disabled">
     <param name="file">*.tar</param>

++++++ _servicedata ++++++
--- /var/tmp/diff_new_pack.5RGT2y/_old  2018-05-07 14:50:40.443665189 +0200
+++ /var/tmp/diff_new_pack.5RGT2y/_new  2018-05-07 14:50:40.447665064 +0200
@@ -1,4 +1,4 @@
 <servicedata>
 <service name="tar_scm">
                 <param 
name="url">https://github.com/ostreedev/ostree.git</param>
-              <param 
name="changesrevision">d3fa95023e1d944f5923064d5b19cc6ee62cf80a</param></service></servicedata>
\ No newline at end of file
+              <param 
name="changesrevision">155c936cd57892adab7b0b4ed4473da7fc45caa3</param></service></servicedata>
\ No newline at end of file

++++++ libostree-2018.1.tar.xz -> libostree-2018.4.tar.xz ++++++
++++ 11627 lines of diff (skipped)


Reply via email to