Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package dwarfs for openSUSE:Factory checked 
in at 2025-09-03 21:07:51
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/dwarfs (Old)
 and      /work/SRC/openSUSE:Factory/.dwarfs.new.1977 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "dwarfs"

Wed Sep  3 21:07:51 2025 rev:5 rq:1302510 version:0.13.0

Changes:
--------
--- /work/SRC/openSUSE:Factory/dwarfs/dwarfs.changes    2025-08-27 
21:36:54.352260034 +0200
+++ /work/SRC/openSUSE:Factory/.dwarfs.new.1977/dwarfs.changes  2025-09-03 
21:08:19.738912433 +0200
@@ -1,0 +2,67 @@
+Tue Sep  2 22:55:02 UTC 2025 - Mia Herkt <[email protected]>
+
+- Update to version 0.13.0:
+Bugfixes:
+  * Made section index discovery more robust.
+    gh#mhx/dwarfs#264
+  * A recent kernel change (https://lkml.org/lkml/2025/5/5/2868)
+    caused the tools_test to fail on Linux 6.14 and later.
+    This has been fixed by accepting both EPERM and ENOSYS as
+    valid error codes for link() calls.
+Features:
+  * Support for big-endian architectures.
+    This is still experimental, even though all unit tests pass
+    with QEMU, and the benchmark suite runs fine on real hardware.
+    This currently requires forked versions of folly and fsst.
+    The changes are small and the pull requests will hopefully be
+    merged upstream soon.
+  * Experimental support for 32-bit architectures.
+    While DwarFS should mostly "just work" on 32-bit when using
+    small images (a few hundred megabytes), the limited address
+    space is a problem for the extensive use of memory-mapped
+    files inside DwarFS. There will be changes to limit the use of
+    mmap in the future (mainly due to other issues), which should
+    help 32-bit compatibility as a side-effect.
+    gh#mhx/dwarfs#268.
+  * The category metadata for categorized blocks is now stored in
+    the metadata block by default. This allows re-compressing the
+    blocks with a metadata-dependent algorithm (e.g. FLAC) even if
+    they were previously compressed using a metadata-independent
+    algorithm.
+    This can be disabled using the --no-category-metadata option.
+    See the mkdwarfs man page for more details.
+  * The --no-category-names and --no-category-metadata options can
+    be used to reduce the size of the metadata. However, this will
+    make it impossible to use metadata-dependent compression
+    algorithms (e.g. FLAC), or even select category-specific
+    compression, when recompressing the image.
+  * Metadata rebuilding is now supported in mkdwarfs using the
+    --rebuild-metadata option. Previously, the metadata could only
+    be recompressed, but it was impossible to change it. With the
+    new option, it is now possible to change metadata packing and
+    apply operations like --set-owner, --set-group, --set-time,
+    --time-resolution, --chmod, or --no-create-timestamp.
+    Note that these are potentially lossy operations that may be
+    irreversible. By default, the history of metadata rebuilds is
+    tracked in the metadata itself, but this can be disabled using
+    --no-metadata-version-history.
+  * In addition to metadata rebuilding, it is now also possible to
+    change the block size of an existing image using the
+    --change-block-size option. This implies --rebuild-metadata
+    and --recompress=all. This can be useful for tuning the
+    performance of an existing image without having to re-create
+    it from scratch.
+  * mkdwarfs now shows its current memory usage while running.
+    Note that -L/--memory-limit still only limits the memory used
+    for the block queue, not the overall memory usage. Fixing this
+    is on the roadmap, there's no need to file an issue.
+  * dwarfsextract has new options to control the output format:
+    --format-options and --format-filters. There is also
+    --format=auto to automatically "guess" the format and filters
+    based on the output file name.
+  * dwarfsck has a new frozen_details detail level that will show
+    the frozen_analysis content ordered by memory location instead
+    of memory usage and also shows the address range of each
+    section.
+
+-------------------------------------------------------------------

Old:
----
  dwarfs-0.12.4.tar.xz

New:
----
  dwarfs-0.13.0.tar.xz

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

Other differences:
------------------
++++++ dwarfs.spec ++++++
--- /var/tmp/diff_new_pack.gJ9SkJ/_old  2025-09-03 21:08:20.526945733 +0200
+++ /var/tmp/diff_new_pack.gJ9SkJ/_new  2025-09-03 21:08:20.526945733 +0200
@@ -19,7 +19,7 @@
 %define sover %(echo %{version} | sed 's/\\./_/g;')
 %define __builder ninja
 Name:           dwarfs
-Version:        0.12.4
+Version:        0.13.0
 Release:        0
 Summary:        Deduplicating compressed read-only file system
 License:        GPL-3.0-or-later AND MIT

++++++ dwarfs-0.12.4.tar.xz -> dwarfs-0.13.0.tar.xz ++++++
/work/SRC/openSUSE:Factory/dwarfs/dwarfs-0.12.4.tar.xz 
/work/SRC/openSUSE:Factory/.dwarfs.new.1977/dwarfs-0.13.0.tar.xz differ: char 
15, line 1

Reply via email to