Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sysroot: Add concept of deployment "pinning" 📌 #1464

Closed
wants to merge 3 commits into from

Commits on Feb 26, 2018

  1. sysroot: Bump mtime when writing an origin file

    This ensures that e.g. `rpm-ostreed` will get notified of the changes.
    cgwalters committed Feb 26, 2018
    Configuration menu
    Copy the full SHA
    8a87b1d View commit details
    Browse the repository at this point in the history
  2. sysroot: Add API to clean up transient keys in origin files

    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.
    cgwalters committed Feb 26, 2018
    Configuration menu
    Copy the full SHA
    6e54bfe View commit details
    Browse the repository at this point in the history
  3. sysroot: Add concept of deployment "pinning" 📌

    Example user story: Jane rebases her OS to a new major version N, and wants to
    keep around N-1 even after a few upgrades for a while so she can easily roll
    back. I plan to add `rpm-ostree rebase --pin` to opt-in to this for example.
    
    Builds on the new `libostree-transient` group to store pinning state there.
    
    Closes: ostreedev#1460
    cgwalters committed Feb 26, 2018
    Configuration menu
    Copy the full SHA
    4374dcf View commit details
    Browse the repository at this point in the history