The `origin/unlocked` and `origin/override-commit` keys are examples of state that's really transient; we don't want to maintain them across upgrades. Right now there are bits for this in both `ostree admin upgrade` as well as in rpm-ostree. This new API will slightly clean up both cases, but it's really prep for adding a concept of deployment "pinning" that will live in the new `libostree-transient` group. Closes: #1464 Approved by: jlebon |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| Makefile.am | ||
| ostree-docs.xml | ||
| ostree-experimental-sections.txt | ||
| ostree-sections.txt | ||