Change Instance

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "unit": "https://translate.fedoraproject.org/api/units/11289145/?format=api",
    "component": "https://translate.fedoraproject.org/api/components/fedora-docs-l10n-fedora-silverblue/masterpagesgetting-started/?format=api",
    "translation": "https://translate.fedoraproject.org/api/translations/fedora-docs-l10n-fedora-silverblue/masterpagesgetting-started/pt_BR/?format=api",
    "user": null,
    "author": null,
    "timestamp": "2022-09-10T22:06:14.682069Z",
    "action": 30,
    "target": "Currently, using package layering creates a new \"deployment\", or bootable filesystem root.  It does not affect your current root.  This preserves rollback and the transactional model, but means that the system must be rebooted after a package has been layered or updated.  You can alternatively use `rpm-ostree install --apply-live <pkg>` to also temporarily apply the change directly to your currently booted deployment.  It's generally expected that you use package layering sparingly, and use `flatpak` and `dnf install` inside a `toolbox` etc.",
    "old": "Currently, using package layering creates a new \"deployment\", or bootable filesystem root.  It does not affect your current root.  This preserves rollback and the transactional model, but means that the system must be rebooted after a package has been layered.  If you don't want to reboot your system for switching to the new deployment, you can use an experimental `rpm-ostree ex apply-live` command to update the filesystem to see changes from new deployment, but it's generally expected that you use package layering sparingly, and use `flatpak` and `dnf install` inside a `toolbox` etc.",
    "details": {},
    "id": 7618335,
    "action_name": "Source string changed",
    "url": "https://translate.fedoraproject.org/api/changes/7618335/?format=api"
}