Hello community,
here is the log from the commit of package libostree for openSUSE:Factory
checked in at 2020-04-13 12:50:04
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/libostree (Old)
and /work/SRC/openSUSE:Factory/.libostree.new.3248 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "libostree"
Mon Apr 13 12:50:04 2020 rev:17 rq:792299 version:2020.3
Changes:
--------
--- /work/SRC/openSUSE:Factory/libostree/libostree.changes 2020-01-18
12:17:23.891115325 +0100
+++ /work/SRC/openSUSE:Factory/.libostree.new.3248/libostree.changes
2020-04-13 12:50:06.744564632 +0200
@@ -1,0 +2,65 @@
+Mon Apr 06 09:39:45 UTC 2020 - alarr...@suse.com
+
+- Update to version 2020.3:
+ * A quick followup to 2020.2, which introduced support for
+ read-only sysroot ended up breaking some of the Fedora CoreOS
+ tests in coreos-assembler which in turn holds back ostree
+ going into FCOS
+ * Now that gap has been closed and more of those tests are being
+ run on the new CI.
+
+- Update to version 2020.2:
+ * lib: Fix Since versions for 2020.1
+ * Post-release version bump
+ * "Brown paper bag" release that actually sets the
+ is_release_build=yes flag and also fixes the Since: on a few
+ new functions.
+
+- Update to version 2020.1:
+ * There is now support for making the /sysroot mount point
+ read-only to start. This protects against a lot of accidental
+ damage, and also generalizes and improves the previous special
+ case handling of having /boot read-only. One known issue is
+ that ostree pull is broken with this enabled, and this will be
+ fixed.
+ * Error-handling around GPG verification has had an overhaul.
+ Specifically, libostree now has more specific error codes to
+ distinguish between different verification failures. This
+ should allow apps to have more fine-grained control over how
+ to respond to errors. Do note that the error messages
+ themselves have changed, and we strongly suggest that anyone
+ relying on a specific error message string to migrate to using
+ the API directly.
+ * The original "archive" (split up objects) format didn't make it
+ easy for a client system to know how much data it would be
+ downloading. Later, static deltas were added which addressed
+ this problem, but there are situations in which object fetches
+ still occur. Later then support for optional sizes metadata in
+ commit objects was added but was never really
+ stabilized/publicized. There were also some bugs in it. That is
+ now completed - the sizes data is now stable. and new API was
+ added to read it.
+ * This release adds initial fs-verity support; it doesn't do too
+ much today. Bigger picture it's important to understand that
+ the vision of OSTree is to enable Linux systems that feel like
+ they're "image based" (transactional, versioned updates, no
+ dependency resolution client side), but also to enable things
+ like doing commits on the client side. Today rpm-ostree
+ supports replacing the kernel client side as a first class
+ operation. This is crucially important to make it feel truly
+ like a Linux system that you own.
+ * A small tweak was made to have OSTree create repo structure
+ directories and files (such as objects/ or .lock) with group
+ write permissions. This is useful for managing OSTree remote
+ servers from multiple UIDs. For systems with the default umask
+ of 0022, this should have no effect.
+ * We've extensively reworked CI for the upstream repo. In
+ addition to Travis, testing is now done on top of Fedora
+ CoreOS. Not all tests have been carried over, but expect to see
+ more coming. This rework will also allow us to have more
+ comprehensive tests previously not possible.
+ * Several fixes were made to the test suite to handle the cases
+ of systemd vs no-systemd, and systemd is now advertised in the
+ list of features in ostree --version if present.
+
+-------------------------------------------------------------------
@@ -23,7 +88,7 @@
- * This is mostly a bugfix release. Notably, the 2019.3 release caused
- some issues related to the gpg-agent code spewing messages on the
- terminal. Additionally, Fedora 31 users have hit upon issues with
- ostree-finalize-staged.service running too late to be able to write
- back its logs to the journal. This then confused rpm-ostree after
- reboot, because it looks at the previous boot's journal for this
- message.
+ * This is mostly a bugfix release. Notably, the 2019.3 release
+ caused some issues related to the gpg-agent code spewing
+ messages on the terminal. Additionally, Fedora 31 users have
+ hit upon issues with ostree-finalize-staged.service running too
+ late to be able to write back its logs to the journal. This
+ then confused rpm-ostree after reboot, because it looks at the
+ previous boot's journal for this message.
@@ -31,8 +96,8 @@
- "reason" so that after ostree fsck --delete was used, subsequent
- ostree fsck will continue to report an error. This should be used
- by higher level tools that want to do "fsck and repair". It's
- likely at some point that "fsck and repair" logic will move down
- into the libostree core as well.
- * There are ongoing efforts to port Fedora CoreOS to s390x: one fix
- landed here to add the deployment prefix to BLS entries since it's
- what the zipl bootloader expected.
+ "reason" so that after ostree fsck --delete was used,
+ subsequent ostree fsck will continue to report an error. This
+ should be used by higher level tools that want to do "fsck and
+ repair". It's likely at some point that "fsck and repair"
+ logic will move down into the libostree core as well.
+ * There are ongoing efforts to port Fedora CoreOS to s390x: one
+ fix landed here to add the deployment prefix to BLS entries
+ since it's what the zipl bootloader expected.
@@ -53,2 +118,3 @@
- + It's been some time since the last release, so this is a slightly
- larger one! There's lots of new features, and a few bug fixes.
+ + It's been some time since the last release, so this is a
+ slightly larger one! There's lots of new features, and a few
+ bug fixes.
@@ -56,7 +122,7 @@
- * A new sysroot.bootloader key was added to be more explicit about
- which bootloader OSTree should use. Notably a none value is
- supported, in which OSTree is solely responsible for writing the
- BLS entries. This can then be used by bootloaders like GRUB2,
- which now supports BLS natively.
- * ostree config now supports the unset command to unset a key from
- the OSTree repo config
+ * A new sysroot.bootloader key was added to be more explicit
+ about which bootloader OSTree should use. Notably a none
+ value is supported, in which OSTree is solely responsible
+ for writing the BLS entries. This can then be used by
+ bootloaders like GRUB2, which now supports BLS natively.
+ * ostree config now supports the unset command to unset a key
+ from the OSTree repo config
@@ -65,4 +131,4 @@
- * ostree-prepare-root now logs a structured journal message after
- finding the deployment to which to pivot. This can be used by
- higher-level apps like RPM-OSTree to build a history of the
- deployments the machine was booted into.
+ * ostree-prepare-root now logs a structured journal message
+ after finding the deployment to which to pivot. This can be
+ used by higher-level apps like RPM-OSTree to build a history
+ of the deployments the machine was booted into.
@@ -70,5 +136,6 @@
- finalization at shutdown. This is intended to be used in systems
- that need more fine-tuned control between staging a deployment,
- and setting it as the default deployment on reboot.
- * ostree static-delta show now prints the From and To commits for
- which the delta was generated
+ finalization at shutdown. This is intended to be used in
+ systems that need more fine-tuned control between staging a
+ deployment, and setting it as the default deployment on
+ reboot.
+ * ostree static-delta show now prints the From and To commits
+ for which the delta was generated
@@ -76,9 +143,10 @@
- * Make looking up collection-refs similar to how regular refs are
- looked up, i.e. first in the transaction, then in the current
- repo, and then in the parent repo
- * Don't include the OSTree commit version number twice in the boot
- menu title. This affected at least Fedora-based systems composed
- with RPM-OSTree's mutate-os-release.
- * Activate ostree-finalize-staged earlier; this should hopefully
- make deployment finalization more reliable by running it later in
- the shutdown sequence, when less services are running
+ * Make looking up collection-refs similar to how regular refs
+ are looked up, i.e. first in the transaction, then in the
+ current repo, and then in the parent repo
+ * Don't include the OSTree commit version number twice in the
+ boot menu title. This affected at least Fedora-based systems
+ composed with RPM-OSTree's mutate-os-release.
+ * Activate ostree-finalize-staged earlier; this should
+ hopefully make deployment finalization more reliable by
+ running it later in the shutdown sequence, when less services
+ are running
@@ -86,3 +154,3 @@
- deployment, rather than the previously deployed tree. This was a
- corner case where the deployment failed if a previous deployment
- did not exist, on systems where grub.cfg is used.
+ deployment, rather than the previously deployed tree. This
+ was a corner case where the deployment failed if a previous
+ deployment did not exist, on systems where grub.cfg is used.
Old:
----
libostree-2019.6.tar.xz
New:
----
libostree-2020.3.tar.xz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ libostree.spec ++++++
--- /var/tmp/diff_new_pack.BEPb3E/_old 2020-04-13 12:50:07.592565109 +0200
+++ /var/tmp/diff_new_pack.BEPb3E/_new 2020-04-13 12:50:07.596565112 +0200
@@ -17,7 +17,7 @@
Name: libostree
-Version: 2019.6
+Version: 2020.3
Release: 0
Summary: Git for operating system binaries
License: LGPL-2.0-or-later
++++++ _service ++++++
--- /var/tmp/diff_new_pack.BEPb3E/_old 2020-04-13 12:50:07.616565123 +0200
+++ /var/tmp/diff_new_pack.BEPb3E/_new 2020-04-13 12:50:07.616565123 +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/v2019.6</param>
+ <param name="revision">refs/tags/v2020.3</param>
</service>
<service name="recompress" mode="disabled">
<param name="file">*.tar</param>
++++++ _servicedata ++++++
--- /var/tmp/diff_new_pack.BEPb3E/_old 2020-04-13 12:50:07.632565132 +0200
+++ /var/tmp/diff_new_pack.BEPb3E/_new 2020-04-13 12:50:07.632565132 +0200
@@ -1,4 +1,4 @@
<servicedata>
<service name="tar_scm">
<param
name="url">https://github.com/ostreedev/ostree.git</param>
- <param
name="changesrevision">978bd19f977119e391a7c4ea706eeb4740970757</param></service></servicedata>
\ No newline at end of file
+ <param
name="changesrevision">6ed48234ba579ff73eb128af237212b0a00f2057</param></service></servicedata>
\ No newline at end of file
++++++ libostree-2019.6.tar.xz -> libostree-2020.3.tar.xz ++++++
++++ 4171 lines of diff (skipped)
