Git for operating system binaries

Edit Package libostree
https://github.com/ostreedev/ostree

OSTree is a tool for managing bootable, immutable, versioned
filesystem trees. While it takes over some of the roles of tradtional
"package managers" like dpkg and rpm, it is not a package system; nor
is it a tool for managing full disk images. Instead, it sits between
those levels, offering a blend of the advantages (and disadvantages)
of both.

Refresh
Refresh
Source Files
Filename Size Changed
_service 0000000623 623 Bytes
_servicedata 0000000237 237 Bytes
libostree-2018.4.tar.xz 0001693576 1.62 MB
libostree.changes 0000069482 67.9 KB
libostree.spec 0000006800 6.64 KB
ostree-grub2-location.patch 0000000471 471 Bytes
Revision 10 (latest revision is 38)
Dominique Leuenberger's avatar Dominique Leuenberger (dimstar_suse) accepted request 603000 from Dominique Leuenberger's avatar Dominique Leuenberger (dimstar) (revision 10)
- 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! (forwarded request 602906 from iznogood)
Comments 0
openSUSE Build Service is sponsored by