libostree 0.2.0

*DEPRECATED* Please use the 'ostree' crate instead failed to build libostree-0.2.0
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure builds.
If you believe this is' fault, open an issue.
Visit the last successful build: libostree-0.1.1


pipeline status master-docs

Note: this crate has been deprecated and renamed to ostree. Please use the ostree crate instead.

Rust bindings for libostree.

libostree is both a shared library and suite of command line tools that combines a "git-like" model for committing and downloading bootable filesystem trees, along with a layer for deploying them and managing the bootloader configuration.


The bindings are quite incomplete right now. Most of it can be autogenerated, but I simply turned on what I needed and left the rest for later.



The libostree crate requires libostree and the libostree development headers. On Debian/Ubuntu, they can be installed with:

$ sudo apt-get install libostree-1 libostree-dev


To use the crate, add it to your Cargo.toml:

libostree = "0.1"

To use features from later libostree versions, you need to specify the release version as well:

version = "0.1"
features = ["v2018_7"]


The libostree and libostree-sys crates can be built and tested using regular Cargo commands.

Generated code

Most code is generated based on the gir files using the gir tool. These parts can be regenerated using the included Makefile:

$ make generate-libostree-sys generate-libostree

Run the following command to update the bundled gir files:

$ make update-gir-files


The libostree API documentation is not included in the code by default because of its LGPL license. This means normal cargo doc runs don't include API docs for the generated code. Run the merge-lgpl-docs Makefile target to include the API docs in the source so they can be consumed by cargo doc:

$ make merge-lgpl-docs

Keep in mind that if you build the crate with the API docs included, it is effectively LGPL-licensed and you need to comply with the LGPL requirements (specifically, allowing users of your end product to swap out the LGPL'd parts).

CI includes the LGPL docs in the documentation build.


Releases can be done using the publish_* jobs in the pipeline. There's no versioning helper yet so version bumps need to be done manually.


The libostree crate is licensed under the MIT license. See the LICENSE file for details.

libostree itself is licensed under the LGPL2+. See its licensing information for more information.