{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiaremfqpz2ty5vqwxsxob4gisrmhlfk7ud4f7766whvvh5ly7gco4",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mgp7h6vnjzc2"
  },
  "path": "/t/release-v4-8-2-mitigate-rpm-ostree-regression-secureblue-secureblue/36143#post_1",
  "publishedAt": "2026-03-10T10:10:44.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "GitHub",
    "Release v4.8.2 - Mitigate rpm-ostree regression · secureblue/secureblue",
    "pinning"
  ],
  "textContent": "GitHub\n\n### Release v4.8.2 - Mitigate rpm-ostree regression · secureblue/secureblue\n\nv4.8.2 - Mitigate rpm-ostree regression Reminder: releases are symbolic. Builds are created and published immediately after new commits are merged. There is a critical rpm-ostree regression in vers...\n\n> There is a critical `rpm-ostree` regression in version 2026.1 causing upgrade failures. To confirm whether you are on the impacted version, check `rpm-ostree --version`. If the version shows 2026.1, follow these mitigation steps verbatim, allowing you to bypass the regression and resume upgrades to the `latest` tag, wherein the issue has already been mitigated by pinning the previous `rpm-ostree` version:\n\n\n    $ run0\n    # rpm-ostree usroverlay\n    # dnf5 install -y --from-repo=updates-archive rpm-ostree-2025.12-1.fc43\n    # ujust update-system\n    # systemctl reboot\n\n\n> We will be working with upstream to help close the gap in continuous integration coverage that allowed this regression to ship.",
  "title": "Release v4.8.2 - Mitigate rpm-ostree regression · secureblue/secureblue"
}