Translation components API.

See the Weblate's Web API documentation for detailed description of the API.

GET /api/translations/debian-handbook/12_advanced-administration/nb_NO/changes/?format=api&page=7
HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "count": 1586,
    "next": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/changes/?format=api&page=8",
    "previous": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/changes/?format=api&page=6",
    "results": [
        {
            "unit": "https://hosted.weblate.org/api/units/82701026/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.184931+02:00",
            "action": 59,
            "target": "<primary>LVM</primary><secondary>opprett PV</secondary>",
            "old": "<primary>LVM</primary><secondary>opprett PV</secondary>",
            "details": {
                "state": 20,
                "source": "<primary>LVM</primary><secondary>create PV</secondary>",
                "old_state": 20
            },
            "id": 35316720,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316720/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701017/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.184870+02:00",
            "action": 59,
            "target": "<primary>LVM</primary><secondary>konsept</secondary>",
            "old": "<primary>LVM</primary><secondary>konsept</secondary>",
            "details": {
                "state": 20,
                "source": "<primary>LVM</primary><secondary>concept</secondary>",
                "old_state": 20
            },
            "id": 35316719,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316719/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701016/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.184808+02:00",
            "action": 59,
            "target": "<computeroutput># </computeroutput><userinput>mdadm --misc --detail --brief /dev/md?\n</userinput><computeroutput>ARRAY /dev/md/0  metadata=1.2 UUID=a75ac628:b384c441:157137ac:c04cd98c name=debian:0\nARRAY /dev/md/1  metadata=1.2 UUID=2dfb7fd5:e09e0527:0b5a905a:8334adb8 name=debian:1\n</computeroutput>",
            "old": "<computeroutput># </computeroutput><userinput>mdadm --misc --detail --brief /dev/md?\n</userinput><computeroutput>ARRAY /dev/md/0  metadata=1.2 UUID=a75ac628:b384c441:157137ac:c04cd98c name=debian:0\nARRAY /dev/md/1  metadata=1.2 UUID=2dfb7fd5:e09e0527:0b5a905a:8334adb8 name=debian:1\n</computeroutput>",
            "details": {
                "state": 20,
                "source": "<computeroutput># </computeroutput><userinput>mdadm --misc --detail --brief /dev/md?\n</userinput><computeroutput>ARRAY /dev/md/0  metadata=1.2 UUID=a75ac628:b384c441:157137ac:c04cd98c name=debian:0\nARRAY /dev/md/1  metadata=1.2 UUID=2dfb7fd5:e09e0527:0b5a905a:8334adb8 name=debian:1\n</computeroutput>",
                "old_state": 20
            },
            "id": 35316718,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316718/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701015/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.184743+02:00",
            "action": 59,
            "target": "<![CDATA[# mdadm.conf\n#\n# !NB! Run update-initramfs -u after updating this file.\n# !NB! This will ensure that initramfs has an uptodate copy.\n#\n# Please refer to mdadm.conf(5) for information about this file.\n#\n\n# by default (built-in), scan all partitions (/proc/partitions) and all\n# containers for MD superblocks. alternatively, specify devices to scan, using\n# wildcards if desired.\nDEVICE /dev/sd*\n\n# automatically tag new arrays as belonging to the local system\nHOMEHOST <system>\n\n# instruct the monitoring daemon where to send mail alerts\nMAILADDR root\n\n# definitions of existing MD arrays\nARRAY /dev/md/0  metadata=1.2 UUID=a75ac628:b384c441:157137ac:c04cd98c name=debian:0\nARRAY /dev/md/1  metadata=1.2 UUID=2dfb7fd5:e09e0527:0b5a905a:8334adb8 name=debian:1\n# This configuration was auto-generated on Mon, 28 Feb 2022 01:53:48 +0100 by mkconf\n]]>",
            "old": "<![CDATA[# mdadm.conf\n#\n# !NB! Run update-initramfs -u after updating this file.\n# !NB! This will ensure that initramfs has an uptodate copy.\n#\n# Please refer to mdadm.conf(5) for information about this file.\n#\n\n# by default (built-in), scan all partitions (/proc/partitions) and all\n# containers for MD superblocks. alternatively, specify devices to scan, using\n# wildcards if desired.\nDEVICE /dev/sd*\n\n# automatically tag new arrays as belonging to the local system\nHOMEHOST <system>\n\n# instruct the monitoring daemon where to send mail alerts\nMAILADDR root\n\n# definitions of existing MD arrays\nARRAY /dev/md/0  metadata=1.2 UUID=a75ac628:b384c441:157137ac:c04cd98c name=debian:0\nARRAY /dev/md/1  metadata=1.2 UUID=2dfb7fd5:e09e0527:0b5a905a:8334adb8 name=debian:1\n# This configuration was auto-generated on Mon, 28 Feb 2022 01:53:48 +0100 by mkconf\n]]>",
            "details": {
                "state": 20,
                "source": "<![CDATA[# mdadm.conf\n#\n# !NB! Run update-initramfs -u after updating this file.\n# !NB! This will ensure that initramfs has an uptodate copy.\n#\n# Please refer to mdadm.conf(5) for information about this file.\n#\n\n# by default (built-in), scan all partitions (/proc/partitions) and all\n# containers for MD superblocks. alternatively, specify devices to scan, using\n# wildcards if desired.\nDEVICE /dev/sd*\n\n# automatically tag new arrays as belonging to the local system\nHOMEHOST <system>\n\n# instruct the monitoring daemon where to send mail alerts\nMAILADDR root\n\n# definitions of existing MD arrays\nARRAY /dev/md/0  metadata=1.2 UUID=a75ac628:b384c441:157137ac:c04cd98c name=debian:0\nARRAY /dev/md/1  metadata=1.2 UUID=2dfb7fd5:e09e0527:0b5a905a:8334adb8 name=debian:1\n# This configuration was auto-generated on Mon, 28 Feb 2022 01:53:48 +0100 by mkconf\n]]>",
                "old_state": 20
            },
            "id": 35316717,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316717/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701013/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.184677+02:00",
            "action": 59,
            "target": "Det meste av meta-dataene som gjelder RAID-volumer lagres direkte på diskene til disse settene, slik at kjernen kan oppdage settene og tilhørende komponenter, og montere dem automatisk når systemet starter opp. Men det oppmuntres til sikkerhetskopiering av dette oppsettet, fordi denne deteksjonen ikke er feilfri, og det er bare å forvente at den vil svikte akkurat under følsomme omstendigheter. I vårt eksempel, hvis en svikt i <filename>sde</filename>-disken hadde vært virkelig (i stedet for simulert), og systemet har blitt startet på nytt uten å fjerne denne <filename>sde</filename>-disken, kunne denne disken bli tatt i bruk igjen etter å ha blitt oppdaget under omstarten. Kjernen vil da ha tre fysiske elementer, som hver utgir seg for å inneholde halvparten av det samme RAID-volumet. I paksis leder dette til at RAID-et starter fra de individuelle diskene vekselvist, og også distribuerer dataene vekselvist, avhengig av hvilken disk som startet RAID-et i degradert modus. En annen kilde til forvirring kan komme når RAID-volumer fra to tjenermaskiner blir samlet inn i en tjenermaskin. Hvis disse settene kjørte normalt før diskene ble flyttet, ville kjernen være i stand til å oppdage og montere parene riktig; men hvis de flyttede diskene var samlet i en <filename>md1</filename> på den gamle tjeneren, og den nye tjeneren allerede har en <filename>md1</filename>, ville et av speilene få nytt navn.",
            "old": "Det meste av meta-dataene som gjelder RAID-volumer lagres direkte på diskene til disse settene, slik at kjernen kan oppdage settene og tilhørende komponenter, og montere dem automatisk når systemet starter opp. Men det oppmuntres til sikkerhetskopiering av dette oppsettet, fordi denne deteksjonen ikke er feilfri, og det er bare å forvente at den vil svikte akkurat under følsomme omstendigheter. I vårt eksempel, hvis en svikt i <filename>sde</filename>-disken hadde vært virkelig (i stedet for simulert), og systemet har blitt startet på nytt uten å fjerne denne <filename>sde</filename>-disken, kunne denne disken bli tatt i bruk igjen etter å ha blitt oppdaget under omstarten. Kjernen vil da ha tre fysiske elementer, som hver utgir seg for å inneholde halvparten av det samme RAID-volumet. I paksis leder dette til at RAID-et starter fra de individuelle diskene vekselvist, og også distribuerer dataene vekselvist, avhengig av hvilken disk som startet RAID-et i degradert modus. En annen kilde til forvirring kan komme når RAID-volumer fra to tjenermaskiner blir samlet inn i en tjenermaskin. Hvis disse settene kjørte normalt før diskene ble flyttet, ville kjernen være i stand til å oppdage og montere parene riktig; men hvis de flyttede diskene var samlet i en <filename>md1</filename> på den gamle tjeneren, og den nye tjeneren allerede har en <filename>md1</filename>, ville et av speilene få nytt navn.",
            "details": {
                "state": 20,
                "source": "Most of the meta-data concerning RAID volumes are saved directly on the disks that make up these arrays, so that the kernel can detect the arrays and their components and assemble them automatically when the system starts up. However, backing up this configuration is encouraged, because this detection isn't fail-proof, and it is only expected that it will fail precisely in sensitive circumstances. In our example, if the <filename>sde</filename> disk failure had been real (instead of simulated) and the system had been restarted without removing this <filename>sde</filename> disk, this disk could start working again due to having been probed during the reboot. The kernel would then have three physical elements, each claiming to contain half of the same RAID volume. In reality this leads to the RAID starting from the individual disks alternately - distributing the data also alternately, depending on which disk started the RAID in degraded mode Another source of confusion can come when RAID volumes from two servers are consolidated onto one server only. If these arrays were running normally before the disks were moved, the kernel would be able to detect and reassemble the pairs properly; but if the moved disks had been aggregated into an <filename>md1</filename> on the old server, and the new server already has an <filename>md1</filename>, one of the mirrors would be renamed.",
                "old_state": 20
            },
            "id": 35316716,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316716/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701012/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.184614+02:00",
            "action": 59,
            "target": "<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --remove /dev/sde\n</userinput><computeroutput>mdadm: hot removed /dev/sde from /dev/md1\n# </computeroutput><userinput>mdadm --detail /dev/md1\n</userinput><computeroutput>/dev/md1:\n[...]\n    Number   Major   Minor   RaidDevice State\n       0       8       34        0      active sync   /dev/sdd2\n       2       8       64        1      active sync   /dev/sdf\n</computeroutput>",
            "old": "<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --remove /dev/sde\n</userinput><computeroutput>mdadm: hot removed /dev/sde from /dev/md1\n# </computeroutput><userinput>mdadm --detail /dev/md1\n</userinput><computeroutput>/dev/md1:\n[...]\n    Number   Major   Minor   RaidDevice State\n       0       8       34        0      active sync   /dev/sdd2\n       2       8       64        1      active sync   /dev/sdf\n</computeroutput>",
            "details": {
                "state": 20,
                "source": "<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --remove /dev/sde\n</userinput><computeroutput>mdadm: hot removed /dev/sde from /dev/md1\n# </computeroutput><userinput>mdadm --detail /dev/md1\n</userinput><computeroutput>/dev/md1:\n[...]\n    Number   Major   Minor   RaidDevice State\n       0       8       34        0      active sync   /dev/sdd2\n       2       8       64        1      active sync   /dev/sdf\n</computeroutput>",
                "old_state": 20
            },
            "id": 35316715,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316715/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701011/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.184541+02:00",
            "action": 59,
            "target": "<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --add /dev/sdf</userinput>\n<computeroutput>mdadm: added /dev/sdf\n# </computeroutput><userinput>mdadm --detail /dev/md1\n</userinput><computeroutput>/dev/md1:\n           Version : 1.2\n     Creation Time : Mon Feb 28 02:07:48 2022\n        Raid Level : raid1\n        Array Size : 4189184 (4.00 GiB 4.29 GB)\n     Used Dev Size : 4189184 (4.00 GiB 4.29 GB)\n      Raid Devices : 2\n     Total Devices : 3\n       Persistence : Superblock is persistent\n\n       Update Time : Mon Feb 28 02:25:34 2022\n             State : clean, degraded, recovering \n    Active Devices : 1\n   Working Devices : 2\n    Failed Devices : 1\n     Spare Devices : 1\n\nConsistency Policy : resync\n\n    Rebuild Status : 47% complete\n\n              Name : debian:1  (local to host debian)\n              UUID : 2dfb7fd5:e09e0527:0b5a905a:8334adb8\n            Events : 39\n\n    Number   Major   Minor   RaidDevice State\n       0       8       34        0      active sync   /dev/sdd2\n       2       8       64        1      spare rebuilding   /dev/sdf\n\n       1       8       48        -      faulty   /dev/sde\n# </computeroutput><userinput>[...]</userinput>\n<computeroutput>[...]\n# </computeroutput><userinput>mdadm --detail /dev/md1</userinput>\n<computeroutput>/dev/md1:\n           Version : 1.2\n     Creation Time : Mon Feb 28 02:07:48 2022\n        Raid Level : raid1\n        Array Size : 4189184 (4.00 GiB 4.29 GB)\n     Used Dev Size : 4189184 (4.00 GiB 4.29 GB)\n      Raid Devices : 2\n     Total Devices : 3\n       Persistence : Superblock is persistent\n\n       Update Time : Mon Feb 28 02:25:34 2022\n             State : clean\n    Active Devices : 2\n   Working Devices : 2\n    Failed Devices : 1\n     Spare Devices : 0\n\nConsistency Policy : resync\n\n              Name : debian:1  (local to host debian)\n              UUID : 2dfb7fd5:e09e0527:0b5a905a:8334adb8\n            Events : 41\n\n    Number   Major   Minor   RaidDevice State\n       0       8       34        0      active sync   /dev/sdd2\n       2       8       64        1      active sync   /dev/sdf\n\n       1       8       48        -      faulty   /dev/sde\n</computeroutput>",
            "old": "<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --add /dev/sdf</userinput>\n<computeroutput>mdadm: added /dev/sdf\n# </computeroutput><userinput>mdadm --detail /dev/md1\n</userinput><computeroutput>/dev/md1:\n           Version : 1.2\n     Creation Time : Mon Feb 28 02:07:48 2022\n        Raid Level : raid1\n        Array Size : 4189184 (4.00 GiB 4.29 GB)\n     Used Dev Size : 4189184 (4.00 GiB 4.29 GB)\n      Raid Devices : 2\n     Total Devices : 3\n       Persistence : Superblock is persistent\n\n       Update Time : Mon Feb 28 02:25:34 2022\n             State : clean, degraded, recovering \n    Active Devices : 1\n   Working Devices : 2\n    Failed Devices : 1\n     Spare Devices : 1\n\nConsistency Policy : resync\n\n    Rebuild Status : 47% complete\n\n              Name : debian:1  (local to host debian)\n              UUID : 2dfb7fd5:e09e0527:0b5a905a:8334adb8\n            Events : 39\n\n    Number   Major   Minor   RaidDevice State\n       0       8       34        0      active sync   /dev/sdd2\n       2       8       64        1      spare rebuilding   /dev/sdf\n\n       1       8       48        -      faulty   /dev/sde\n# </computeroutput><userinput>[...]</userinput>\n<computeroutput>[...]\n# </computeroutput><userinput>mdadm --detail /dev/md1</userinput>\n<computeroutput>/dev/md1:\n           Version : 1.2\n     Creation Time : Mon Feb 28 02:07:48 2022\n        Raid Level : raid1\n        Array Size : 4189184 (4.00 GiB 4.29 GB)\n     Used Dev Size : 4189184 (4.00 GiB 4.29 GB)\n      Raid Devices : 2\n     Total Devices : 3\n       Persistence : Superblock is persistent\n\n       Update Time : Mon Feb 28 02:25:34 2022\n             State : clean\n    Active Devices : 2\n   Working Devices : 2\n    Failed Devices : 1\n     Spare Devices : 0\n\nConsistency Policy : resync\n\n              Name : debian:1  (local to host debian)\n              UUID : 2dfb7fd5:e09e0527:0b5a905a:8334adb8\n            Events : 41\n\n    Number   Major   Minor   RaidDevice State\n       0       8       34        0      active sync   /dev/sdd2\n       2       8       64        1      active sync   /dev/sdf\n\n       1       8       48        -      faulty   /dev/sde\n</computeroutput>",
            "details": {
                "state": 20,
                "source": "<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --add /dev/sdf</userinput>\n<computeroutput>mdadm: added /dev/sdf\n# </computeroutput><userinput>mdadm --detail /dev/md1\n</userinput><computeroutput>/dev/md1:\n           Version : 1.2\n     Creation Time : Mon Feb 28 02:07:48 2022\n        Raid Level : raid1\n        Array Size : 4189184 (4.00 GiB 4.29 GB)\n     Used Dev Size : 4189184 (4.00 GiB 4.29 GB)\n      Raid Devices : 2\n     Total Devices : 3\n       Persistence : Superblock is persistent\n\n       Update Time : Mon Feb 28 02:25:34 2022\n             State : clean, degraded, recovering \n    Active Devices : 1\n   Working Devices : 2\n    Failed Devices : 1\n     Spare Devices : 1\n\nConsistency Policy : resync\n\n    Rebuild Status : 47% complete\n\n              Name : debian:1  (local to host debian)\n              UUID : 2dfb7fd5:e09e0527:0b5a905a:8334adb8\n            Events : 39\n\n    Number   Major   Minor   RaidDevice State\n       0       8       34        0      active sync   /dev/sdd2\n       2       8       64        1      spare rebuilding   /dev/sdf\n\n       1       8       48        -      faulty   /dev/sde\n# </computeroutput><userinput>[...]</userinput>\n<computeroutput>[...]\n# </computeroutput><userinput>mdadm --detail /dev/md1</userinput>\n<computeroutput>/dev/md1:\n           Version : 1.2\n     Creation Time : Mon Feb 28 02:07:48 2022\n        Raid Level : raid1\n        Array Size : 4189184 (4.00 GiB 4.29 GB)\n     Used Dev Size : 4189184 (4.00 GiB 4.29 GB)\n      Raid Devices : 2\n     Total Devices : 3\n       Persistence : Superblock is persistent\n\n       Update Time : Mon Feb 28 02:25:34 2022\n             State : clean\n    Active Devices : 2\n   Working Devices : 2\n    Failed Devices : 1\n     Spare Devices : 0\n\nConsistency Policy : resync\n\n              Name : debian:1  (local to host debian)\n              UUID : 2dfb7fd5:e09e0527:0b5a905a:8334adb8\n            Events : 41\n\n    Number   Major   Minor   RaidDevice State\n       0       8       34        0      active sync   /dev/sdd2\n       2       8       64        1      active sync   /dev/sdf\n\n       1       8       48        -      faulty   /dev/sde\n</computeroutput>",
                "old_state": 20
            },
            "id": 35316714,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316714/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701010/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.184476+02:00",
            "action": 59,
            "target": "<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --fail /dev/sde\n</userinput><computeroutput>mdadm: set /dev/sde faulty in /dev/md1\n# </computeroutput><userinput>mdadm --detail /dev/md1\n</userinput><computeroutput>/dev/md1:\n           Version : 1.2\n     Creation Time : Mon Feb 28 02:07:48 2022\n        Raid Level : raid1\n        Array Size : 4189184 (4.00 GiB 4.29 GB)\n     Used Dev Size : 4189184 (4.00 GiB 4.29 GB)\n      Raid Devices : 2\n     Total Devices : 2\n       Persistence : Superblock is persistent\n\n       Update Time : Mon Feb 28 02:15:34 2022\n             State : clean, degraded \n    Active Devices : 1\n   Working Devices : 1\n    Failed Devices : 1\n     Spare Devices : 0\n\nConsistency Policy : resync\n\n              Name : debian:1  (local to host debian)\n              UUID : 2dfb7fd5:e09e0527:0b5a905a:8334adb8\n            Events : 19\n\n    Number   Major   Minor   RaidDevice State\n       0       8       34        0      active sync   /dev/sdd2\n       -       0        0        1      removed\n\n       1       8       48        -      faulty   /dev/sde\n</computeroutput>",
            "old": "<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --fail /dev/sde\n</userinput><computeroutput>mdadm: set /dev/sde faulty in /dev/md1\n# </computeroutput><userinput>mdadm --detail /dev/md1\n</userinput><computeroutput>/dev/md1:\n           Version : 1.2\n     Creation Time : Mon Feb 28 02:07:48 2022\n        Raid Level : raid1\n        Array Size : 4189184 (4.00 GiB 4.29 GB)\n     Used Dev Size : 4189184 (4.00 GiB 4.29 GB)\n      Raid Devices : 2\n     Total Devices : 2\n       Persistence : Superblock is persistent\n\n       Update Time : Mon Feb 28 02:15:34 2022\n             State : clean, degraded \n    Active Devices : 1\n   Working Devices : 1\n    Failed Devices : 1\n     Spare Devices : 0\n\nConsistency Policy : resync\n\n              Name : debian:1  (local to host debian)\n              UUID : 2dfb7fd5:e09e0527:0b5a905a:8334adb8\n            Events : 19\n\n    Number   Major   Minor   RaidDevice State\n       0       8       34        0      active sync   /dev/sdd2\n       -       0        0        1      removed\n\n       1       8       48        -      faulty   /dev/sde\n</computeroutput>",
            "details": {
                "state": 20,
                "source": "<computeroutput># </computeroutput><userinput>mdadm /dev/md1 --fail /dev/sde\n</userinput><computeroutput>mdadm: set /dev/sde faulty in /dev/md1\n# </computeroutput><userinput>mdadm --detail /dev/md1\n</userinput><computeroutput>/dev/md1:\n           Version : 1.2\n     Creation Time : Mon Feb 28 02:07:48 2022\n        Raid Level : raid1\n        Array Size : 4189184 (4.00 GiB 4.29 GB)\n     Used Dev Size : 4189184 (4.00 GiB 4.29 GB)\n      Raid Devices : 2\n     Total Devices : 2\n       Persistence : Superblock is persistent\n\n       Update Time : Mon Feb 28 02:15:34 2022\n             State : clean, degraded \n    Active Devices : 1\n   Working Devices : 1\n    Failed Devices : 1\n     Spare Devices : 0\n\nConsistency Policy : resync\n\n              Name : debian:1  (local to host debian)\n              UUID : 2dfb7fd5:e09e0527:0b5a905a:8334adb8\n            Events : 19\n\n    Number   Major   Minor   RaidDevice State\n       0       8       34        0      active sync   /dev/sdd2\n       -       0        0        1      removed\n\n       1       8       48        -      faulty   /dev/sde\n</computeroutput>",
                "old_state": 20
            },
            "id": 35316713,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316713/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701008/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.184415+02:00",
            "action": 59,
            "target": "Som illustrert i eksempelet vårt, kan RAID-enheter lages fra diskpartisjoner også, og krever ikke hele disker.",
            "old": "Som illustrert i eksempelet vårt, kan RAID-enheter lages fra diskpartisjoner også, og krever ikke hele disker.",
            "details": {
                "state": 20,
                "source": "As illustrated by our example, RAID devices can be constructed out of disk partitions as well, and do not require full disks.",
                "old_state": 20
            },
            "id": 35316712,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316712/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701007/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.184345+02:00",
            "action": 59,
            "target": "<computeroutput># </computeroutput><userinput>mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sdd2 /dev/sde\n</userinput><computeroutput>mdadm: Note: this array has metadata at the start and\n    may not be suitable as a boot device.  If you plan to\n    store '/boot' on this device please ensure that\n    your boot-loader understands md/v1.x metadata, or use\n    --metadata=0.90\nmdadm: largest drive (/dev/sdc2) exceeds size (4189184K) by more than 1%\nContinue creating array? </computeroutput><userinput>y\n</userinput><computeroutput>mdadm: Defaulting to version 1.2 metadata\nmdadm: array /dev/md1 started.\n# </computeroutput><userinput>mdadm --query /dev/md1\n</userinput><computeroutput>/dev/md1: 4.00GiB raid1 2 devices, 0 spares. Use mdadm --detail for more detail.\n# </computeroutput><userinput>mdadm --detail /dev/md1\n</userinput><computeroutput>/dev/md1:\n           Version : 1.2\n     Creation Time : Mon Feb 28 02:07:48 2022\n        Raid Level : raid1\n        Array Size : 4189184 (4.00 GiB 4.29 GB)\n     Used Dev Size : 4189184 (4.00 GiB 4.29 GB)\n      Raid Devices : 2\n     Total Devices : 2\n       Persistence : Superblock is persistent\n\n       Update Time : Mon Feb 28 02:08:09 2022\n             State : clean, resync\n    Active Devices : 2\n   Working Devices : 2\n    Failed Devices : 0\n     Spare Devices : 0\n\nConsistency Policy : resync\n\n    Rebuild Status : 13% complete\n\n              Name : debian:1  (local to host debian)\n              UUID : 2dfb7fd5:e09e0527:0b5a905a:8334adb8\n            Events : 17\n\n    Number   Major   Minor   RaidDevice State\n       0       8       34        0      active sync   /dev/sdd2\n       1       8       48        1      active sync   /dev/sde\n# </computeroutput><userinput>mdadm --detail /dev/md1\n</userinput><computeroutput>/dev/md1:\n[...]\n          State : clean\n[...]\n</computeroutput>",
            "old": "<computeroutput># </computeroutput><userinput>mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sdd2 /dev/sde\n</userinput><computeroutput>mdadm: Note: this array has metadata at the start and\n    may not be suitable as a boot device.  If you plan to\n    store '/boot' on this device please ensure that\n    your boot-loader understands md/v1.x metadata, or use\n    --metadata=0.90\nmdadm: largest drive (/dev/sdc2) exceeds size (4189184K) by more than 1%\nContinue creating array? </computeroutput><userinput>y\n</userinput><computeroutput>mdadm: Defaulting to version 1.2 metadata\nmdadm: array /dev/md1 started.\n# </computeroutput><userinput>mdadm --query /dev/md1\n</userinput><computeroutput>/dev/md1: 4.00GiB raid1 2 devices, 0 spares. Use mdadm --detail for more detail.\n# </computeroutput><userinput>mdadm --detail /dev/md1\n</userinput><computeroutput>/dev/md1:\n           Version : 1.2\n     Creation Time : Mon Feb 28 02:07:48 2022\n        Raid Level : raid1\n        Array Size : 4189184 (4.00 GiB 4.29 GB)\n     Used Dev Size : 4189184 (4.00 GiB 4.29 GB)\n      Raid Devices : 2\n     Total Devices : 2\n       Persistence : Superblock is persistent\n\n       Update Time : Mon Feb 28 02:08:09 2022\n             State : clean, resync\n    Active Devices : 2\n   Working Devices : 2\n    Failed Devices : 0\n     Spare Devices : 0\n\nConsistency Policy : resync\n\n    Rebuild Status : 13% complete\n\n              Name : debian:1  (local to host debian)\n              UUID : 2dfb7fd5:e09e0527:0b5a905a:8334adb8\n            Events : 17\n\n    Number   Major   Minor   RaidDevice State\n       0       8       34        0      active sync   /dev/sdd2\n       1       8       48        1      active sync   /dev/sde\n# </computeroutput><userinput>mdadm --detail /dev/md1\n</userinput><computeroutput>/dev/md1:\n[...]\n          State : clean\n[...]\n</computeroutput>",
            "details": {
                "state": 20,
                "source": "<computeroutput># </computeroutput><userinput>mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sdd2 /dev/sde\n</userinput><computeroutput>mdadm: Note: this array has metadata at the start and\n    may not be suitable as a boot device.  If you plan to\n    store '/boot' on this device please ensure that\n    your boot-loader understands md/v1.x metadata, or use\n    --metadata=0.90\nmdadm: largest drive (/dev/sdc2) exceeds size (4189184K) by more than 1%\nContinue creating array? </computeroutput><userinput>y\n</userinput><computeroutput>mdadm: Defaulting to version 1.2 metadata\nmdadm: array /dev/md1 started.\n# </computeroutput><userinput>mdadm --query /dev/md1\n</userinput><computeroutput>/dev/md1: 4.00GiB raid1 2 devices, 0 spares. Use mdadm --detail for more detail.\n# </computeroutput><userinput>mdadm --detail /dev/md1\n</userinput><computeroutput>/dev/md1:\n           Version : 1.2\n     Creation Time : Mon Feb 28 02:07:48 2022\n        Raid Level : raid1\n        Array Size : 4189184 (4.00 GiB 4.29 GB)\n     Used Dev Size : 4189184 (4.00 GiB 4.29 GB)\n      Raid Devices : 2\n     Total Devices : 2\n       Persistence : Superblock is persistent\n\n       Update Time : Mon Feb 28 02:08:09 2022\n             State : clean, resync\n    Active Devices : 2\n   Working Devices : 2\n    Failed Devices : 0\n     Spare Devices : 0\n\nConsistency Policy : resync\n\n    Rebuild Status : 13% complete\n\n              Name : debian:1  (local to host debian)\n              UUID : 2dfb7fd5:e09e0527:0b5a905a:8334adb8\n            Events : 17\n\n    Number   Major   Minor   RaidDevice State\n       0       8       34        0      active sync   /dev/sdd2\n       1       8       48        1      active sync   /dev/sde\n# </computeroutput><userinput>mdadm --detail /dev/md1\n</userinput><computeroutput>/dev/md1:\n[...]\n          State : clean\n[...]\n</computeroutput>",
                "old_state": 20
            },
            "id": 35316711,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316711/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701006/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.184271+02:00",
            "action": 59,
            "target": "<computeroutput># </computeroutput><userinput>mdadm --create /dev/md0 --level=0 --raid-devices=2 /dev/sdb /dev/sdc\n</userinput><computeroutput>mdadm: Defaulting to version 1.2 metadata\nmdadm: array /dev/md0 started.\n# </computeroutput><userinput>mdadm --query /dev/md0\n</userinput><computeroutput>/dev/md0: 7.99GiB raid0 2 devices, 0 spares. Use mdadm --detail for more detail.\n# </computeroutput><userinput>mdadm --detail /dev/md0\n</userinput><computeroutput>/dev/md0:\n           Version : 1.2\n     Creation Time : Mon Feb 28 01:54:24 2022\n        Raid Level : raid0\n        Array Size : 8378368 (7.99 GiB 8.58 GB)\n      Raid Devices : 2\n     Total Devices : 2\n       Persistence : Superblock is persistent\n\n       Update Time : Mon Feb 28 01:54:24 2022\n             State : clean \n    Active Devices : 2\n   Working Devices : 2\n    Failed Devices : 0\n     Spare Devices : 0\n\n            Layout : -unknown-\n        Chunk Size : 512K\n\nConsistency Policy : none\n\n              Name : debian:0  (local to host debian)\n              UUID : a75ac628:b384c441:157137ac:c04cd98c\n            Events : 0\n\n    Number   Major   Minor   RaidDevice State\n       0       8        0        0      active sync   /dev/sdb\n       1       8       16        1      active sync   /dev/sdc\n# </computeroutput><userinput>mkfs.ext4 /dev/md0\n</userinput><computeroutput>mke2fs 1.46.2 (28-Feb-2021)\nDiscarding device blocks: done                            \nCreating filesystem with 2094592 4k blocks and 524288 inodes\nFilesystem UUID: ef077204-c477-4430-bf01-52288237bea0\nSuperblock backups stored on blocks: \n\t32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632\n\nAllocating group tables: done                            \nWriting inode tables: done                            \nCreating journal (16384 blocks): done\nWriting superblocks and filesystem accounting information: done \n\n# </computeroutput><userinput>mkdir /srv/raid-0\n</userinput><computeroutput># </computeroutput><userinput>mount /dev/md0 /srv/raid-0\n</userinput><computeroutput># </computeroutput><userinput>df -h /srv/raid-0\n</userinput><computeroutput>Filesystem      Size  Used Avail Use% Mounted on\n/dev/md0        7.8G   24K  7.4G   1% /srv/raid-0\n</computeroutput>",
            "old": "<computeroutput># </computeroutput><userinput>mdadm --create /dev/md0 --level=0 --raid-devices=2 /dev/sdb /dev/sdc\n</userinput><computeroutput>mdadm: Defaulting to version 1.2 metadata\nmdadm: array /dev/md0 started.\n# </computeroutput><userinput>mdadm --query /dev/md0\n</userinput><computeroutput>/dev/md0: 7.99GiB raid0 2 devices, 0 spares. Use mdadm --detail for more detail.\n# </computeroutput><userinput>mdadm --detail /dev/md0\n</userinput><computeroutput>/dev/md0:\n           Version : 1.2\n     Creation Time : Mon Feb 28 01:54:24 2022\n        Raid Level : raid0\n        Array Size : 8378368 (7.99 GiB 8.58 GB)\n      Raid Devices : 2\n     Total Devices : 2\n       Persistence : Superblock is persistent\n\n       Update Time : Mon Feb 28 01:54:24 2022\n             State : clean \n    Active Devices : 2\n   Working Devices : 2\n    Failed Devices : 0\n     Spare Devices : 0\n\n            Layout : -unknown-\n        Chunk Size : 512K\n\nConsistency Policy : none\n\n              Name : debian:0  (local to host debian)\n              UUID : a75ac628:b384c441:157137ac:c04cd98c\n            Events : 0\n\n    Number   Major   Minor   RaidDevice State\n       0       8        0        0      active sync   /dev/sdb\n       1       8       16        1      active sync   /dev/sdc\n# </computeroutput><userinput>mkfs.ext4 /dev/md0\n</userinput><computeroutput>mke2fs 1.46.2 (28-Feb-2021)\nDiscarding device blocks: done                            \nCreating filesystem with 2094592 4k blocks and 524288 inodes\nFilesystem UUID: ef077204-c477-4430-bf01-52288237bea0\nSuperblock backups stored on blocks: \n\t32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632\n\nAllocating group tables: done                            \nWriting inode tables: done                            \nCreating journal (16384 blocks): done\nWriting superblocks and filesystem accounting information: done \n\n# </computeroutput><userinput>mkdir /srv/raid-0\n</userinput><computeroutput># </computeroutput><userinput>mount /dev/md0 /srv/raid-0\n</userinput><computeroutput># </computeroutput><userinput>df -h /srv/raid-0\n</userinput><computeroutput>Filesystem      Size  Used Avail Use% Mounted on\n/dev/md0        7.8G   24K  7.4G   1% /srv/raid-0\n</computeroutput>",
            "details": {
                "state": 20,
                "source": "<computeroutput># </computeroutput><userinput>mdadm --create /dev/md0 --level=0 --raid-devices=2 /dev/sdb /dev/sdc\n</userinput><computeroutput>mdadm: Defaulting to version 1.2 metadata\nmdadm: array /dev/md0 started.\n# </computeroutput><userinput>mdadm --query /dev/md0\n</userinput><computeroutput>/dev/md0: 7.99GiB raid0 2 devices, 0 spares. Use mdadm --detail for more detail.\n# </computeroutput><userinput>mdadm --detail /dev/md0\n</userinput><computeroutput>/dev/md0:\n           Version : 1.2\n     Creation Time : Mon Feb 28 01:54:24 2022\n        Raid Level : raid0\n        Array Size : 8378368 (7.99 GiB 8.58 GB)\n      Raid Devices : 2\n     Total Devices : 2\n       Persistence : Superblock is persistent\n\n       Update Time : Mon Feb 28 01:54:24 2022\n             State : clean \n    Active Devices : 2\n   Working Devices : 2\n    Failed Devices : 0\n     Spare Devices : 0\n\n            Layout : -unknown-\n        Chunk Size : 512K\n\nConsistency Policy : none\n\n              Name : debian:0  (local to host debian)\n              UUID : a75ac628:b384c441:157137ac:c04cd98c\n            Events : 0\n\n    Number   Major   Minor   RaidDevice State\n       0       8        0        0      active sync   /dev/sdb\n       1       8       16        1      active sync   /dev/sdc\n# </computeroutput><userinput>mkfs.ext4 /dev/md0\n</userinput><computeroutput>mke2fs 1.46.2 (28-Feb-2021)\nDiscarding device blocks: done                            \nCreating filesystem with 2094592 4k blocks and 524288 inodes\nFilesystem UUID: ef077204-c477-4430-bf01-52288237bea0\nSuperblock backups stored on blocks: \n\t32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632\n\nAllocating group tables: done                            \nWriting inode tables: done                            \nCreating journal (16384 blocks): done\nWriting superblocks and filesystem accounting information: done \n\n# </computeroutput><userinput>mkdir /srv/raid-0\n</userinput><computeroutput># </computeroutput><userinput>mount /dev/md0 /srv/raid-0\n</userinput><computeroutput># </computeroutput><userinput>df -h /srv/raid-0\n</userinput><computeroutput>Filesystem      Size  Used Avail Use% Mounted on\n/dev/md0        7.8G   24K  7.4G   1% /srv/raid-0\n</computeroutput>",
                "old_state": 20
            },
            "id": 35316710,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316710/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82700995/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.184212+02:00",
            "action": 59,
            "target": "<emphasis>HUSK</emphasis> RAID er ikke det samme som sikkerhetskopi",
            "old": "<emphasis>HUSK</emphasis> RAID er ikke det samme som sikkerhetskopi",
            "details": {
                "state": 20,
                "source": "<emphasis>CAUTION</emphasis> RAID is not Backup",
                "old_state": 20
            },
            "id": 35316709,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316709/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82700993/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.184153+02:00",
            "action": 59,
            "target": "<primary>RAID</primary><secondary>speil</secondary>",
            "old": "<primary>RAID</primary><secondary>speil</secondary>",
            "details": {
                "state": 20,
                "source": "<primary>RAID</primary><secondary>mirror</secondary>",
                "old_state": 20
            },
            "id": 35316708,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316708/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82700992/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.184093+02:00",
            "action": 59,
            "target": "<primary>RAID</primary><secondary>1</secondary>",
            "old": "<primary>RAID</primary><secondary>1</secondary>",
            "details": {
                "state": 20,
                "source": "<primary>RAID</primary><secondary>1</secondary>",
                "old_state": 20
            },
            "id": 35316707,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316707/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82700991/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.184034+02:00",
            "action": 59,
            "target": "<primary>RAID</primary><secondary>0</secondary>",
            "old": "<primary>RAID</primary><secondary>0</secondary>",
            "details": {
                "state": 20,
                "source": "<primary>RAID</primary><secondary>0</secondary>",
                "old_state": 20
            },
            "id": 35316706,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316706/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82700990/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.183975+02:00",
            "action": 59,
            "target": "<primary>RAID</primary><secondary>stripinger</secondary>",
            "old": "<primary>RAID</primary><secondary>stripinger</secondary>",
            "details": {
                "state": 20,
                "source": "<primary>RAID</primary><secondary>stripes</secondary>",
                "old_state": 20
            },
            "id": 35316705,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316705/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82700989/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.183915+02:00",
            "action": 59,
            "target": "<primary>RAID</primary><secondary>lineært</secondary>",
            "old": "<primary>RAID</primary><secondary>lineært</secondary>",
            "details": {
                "state": 20,
                "source": "<primary>RAID</primary><secondary>linear</secondary>",
                "old_state": 20
            },
            "id": 35316704,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316704/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82700987/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.183824+02:00",
            "action": 59,
            "target": "<primary>RAID</primary><secondary>rekonstruksjon</secondary>",
            "old": "<primary>RAID</primary><secondary>rekonstruksjon</secondary>",
            "details": {
                "state": 20,
                "source": "<primary>RAID</primary><secondary>reconstruction</secondary>",
                "old_state": 20
            },
            "id": 35316703,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316703/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82700986/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.183737+02:00",
            "action": 59,
            "target": "<primary>RAID</primary><secondary>degradert</secondary>",
            "old": "<primary>RAID</primary><secondary>degradert</secondary>",
            "details": {
                "state": 20,
                "source": "<primary>RAID</primary><secondary>degraded</secondary>",
                "old_state": 20
            },
            "id": 35316702,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316702/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82700981/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.183643+02:00",
            "action": 59,
            "target": "Mens LVM og RAID er to forskjellige kjerne-delsystemer som ligger mellom disk-blokk-enheter og filsystemene deres, er <emphasis>btrfs</emphasis> et filsystem, opprinnelig utviklet i Oracle, som skal kombinere egenskapene til LVM og RAID, og mye mer. <ulink type=\"block\" url=\"https://btrfs.wiki.kernel.org/\" />",
            "old": "Mens LVM og RAID er to forskjellige kjerne-delsystemer som ligger mellom disk-blokk-enheter og filsystemene deres, er <emphasis>btrfs</emphasis> et filsystem, opprinnelig utviklet i Oracle, som skal kombinere egenskapene til LVM og RAID, og mye mer. <ulink type=\"block\" url=\"https://btrfs.wiki.kernel.org/\" />",
            "details": {
                "state": 20,
                "source": "While LVM and RAID are two distinct kernel subsystems that come between the disk block devices and their filesystems, <emphasis>btrfs</emphasis> is a filesystem, initially developed at Oracle, that purports to combine the feature sets of LVM and RAID and much more. <ulink type=\"block\" url=\"https://btrfs.wiki.kernel.org/\" />",
                "old_state": 20
            },
            "id": 35316701,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316701/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82700978/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.183548+02:00",
            "action": 59,
            "target": "<primary>dataområde</primary><secondary>håndtering</secondary>",
            "old": "<primary>dataområde</primary><secondary>håndtering</secondary>",
            "details": {
                "state": 20,
                "source": "<primary>volume</primary><secondary>management</secondary>",
                "old_state": 20
            },
            "id": 35316700,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316700/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82700977/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": null,
            "author": null,
            "timestamp": "2022-09-27T17:58:40.183409+02:00",
            "action": 59,
            "target": "Disse teknologiene ble i <xref linkend=\"installation\" /> presentert slik de ser ut fra installasjonsprogrammet, og hvordan de kan integreres til å gjøre utrullingen lett å komme igang med. Etter den første installasjonen, må en administrator kunne håndtere endring av lagringsplassbehov uten å måtte ty til en kostbar reinstallasjon. En må derfor forstå verktøyene som trengs for å håndtere RAID- og LVM-diskområder.",
            "old": "Disse teknologiene ble i <xref linkend=\"installation\" /> presentert slik de ser ut fra installasjonsprogrammet, og hvordan de kan integreres til å gjøre utrullingen lett å komme igang med. Etter den første installasjonen, må en administrator kunne håndtere endring av lagringsplassbehov uten å måtte ty til en kostbar reinstallasjon. En må derfor forstå verktøyene som trengs for å håndtere RAID- og LVM-diskområder.",
            "details": {
                "state": 20,
                "source": "<xref linkend=\"installation\" /> presented these technologies from the point of view of the installer, and how it integrated them to make their deployment easy from the start. After the initial installation, an administrator must be able to handle evolving storage space needs without having to resort to an expensive re-installation. They must therefore understand the required tools for manipulating RAID and LVM volumes.",
                "old_state": 20
            },
            "id": 35316699,
            "action_name": "String updated in the repository",
            "url": "https://hosted.weblate.org/api/changes/35316699/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701242/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:48:18.140874+02:00",
            "action": 2,
            "target": "Munin inkluderer detaljert dokumentasjon om hvordan programtilleggene skal fungere, og hvordan man kan utvikle nye programtillegg. <ulink type=\"block\" url=\"https://guide.munin-monitoring.org/en/latest/plugin/writing.html\" />",
            "old": "Munin inkluderer detaljert dokumentasjon om hvordan programtilleggene skal fungere, og hvordan man kan utvikle nye programtillegg. <ulink type=\"block\" url=\"http://guide.munin-monitoring.org/en/latest/plugin/writing.html\" />",
            "details": {
                "state": 20,
                "source": "Munin does include detailed documentation on how plugins should behave, and how to develop new plugins. <ulink type=\"block\" url=\"https://guide.munin-monitoring.org/en/latest/plugin/writing.html\" />",
                "old_state": 10
            },
            "id": 35267969,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267969/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701174/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:43:04.668331+02:00",
            "action": 2,
            "target": "Prosedyren krever bruk av <command>rpm</command> for å pakke ut et innledende sett med filer, medregnet spesielt <command>yum</command>-oppsettsfiler, og så påkalle <command>yum4</command> for å pakke opp de gjenværende pakkesettene. Men siden vi kaller <command>yum4</command> fra utsiden av chrooten, trenger vi å gjøre noen midlertidige endringer. I eksemplet nedenfor, er mål-chrooten <filename>/srv/centos</filename>.",
            "old": "Prosedyren krever bruk av <command>rpm</command> for å pakke ut et innledende sett med filer, medregnet spesielt <command>yum</command>-oppsettsfiler, og så påkalle <command>yum</command> for å pakke opp de gjenværende pakkesettene. Men siden vi kaller <command>yum</command> fra utsiden av chrooten, trenger vi å gjøre noen midlertidige endringer. I eksemplet nedenfor, er mål-chrooten <filename>/srv/centos</filename>.",
            "details": {
                "state": 20,
                "source": "The procedure requires using <command>rpm</command> to extract an initial set of files, including notably <command>yum</command> configuration files, and then calling <command>yum4</command> to extract the remaining set of packages. But since we call <command>yum4</command> from outside the chroot, we need to make some temporary changes. In the sample below, the target chroot is <filename>/srv/centos</filename>.",
                "old_state": 10
            },
            "id": 35267869,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267869/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701188/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:43:04.617013+02:00",
            "action": 2,
            "target": "Så snart profilene er definert, genererer <command>fai-setup</command>-kommandoen de elementene som kreves for å starte en FAI-installasjon; Dette betyr stort sett å forberede eller å oppdatere et minimalt system (NFS-root) som brukes under installasjonen. Et alternativ er å generere en dedikert oppstarts-CD med <command>fai-cd</command>.",
            "old": "Så snart profilene er definert, genererer <command>fai-setup</command>-kommandoen de elementene som kreves for å starte en FAI-installasjon; Dette betyr stort sett å forberede eller å oppdatere et minimalt system (NFS-root) som brukes under installasjonen. Et alternativ er å generere en dedikert oppstarts-CD med <command>fai-cd</command>.",
            "details": {
                "state": 20,
                "source": "Once the profiles are defined, the <command>fai-setup</command> command generates the elements required to start an FAI installation; this mostly means preparing or updating a minimal system (NFS-root) used during installation. An alternative is to generate a dedicated boot CD with <command>fai-cd</command>.",
                "old_state": 10
            },
            "id": 35267868,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267868/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:42:37.591605+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige programmet har blitt fjernet fra Debian i forkant av utgivelsen av <emphasis role=\"distribution\">Bullseye</emphasis> fordi det ikke ble vedlikeholdt, var utdatert, og foreldet i favør av <command>dnf</command>.",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige programmet har blitt fjernet fra Debian i forkant av utgivelsen av <emphasis role=\"distribution\">Bullseye</emphasis> fordi det ikke ble vedlikeholdt, var utdatert, og foreldet i favør av <command>dnf",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267867,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267867/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:42:36.094310+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige programmet har blitt fjernet fra Debian i forkant av utgivelsen av <emphasis role=\"distribution\">Bullseye</emphasis> fordi det ikke ble vedlikeholdt, var utdatert, og foreldet i favør av <command>dnf",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige programmet har blitt fjernet fra Debian i forkant av utgivelsen av <emphasis role=\"distribution\">Bullseye</emphasis> fordi det ikke ble vedlikeholdt, var utdatert, og foreldet i favør av",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267866,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267866/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:42:34.154647+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige programmet har blitt fjernet fra Debian i forkant av utgivelsen av <emphasis role=\"distribution\">Bullseye</emphasis> fordi det ikke ble vedlikeholdt, var utdatert, og foreldet i favør av",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige programmet har blitt fjernet fra Debian i forkant av utgivelsen av <emphasis role=\"distribution\">Bullseye</emphasis> for",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267865,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267865/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:42:14.608635+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige programmet har blitt fjernet fra Debian i forkant av utgivelsen av <emphasis role=\"distribution\">Bullseye</emphasis> for",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige programmet har blitt fjernet fra Debian i forkant av utgivelsen av <emphasis role=\"distribution\">Bullseye",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267863,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267863/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:42:12.821457+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige programmet har blitt fjernet fra Debian i forkant av utgivelsen av <emphasis role=\"distribution\">Bullseye",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige programmet har blitt fjernet fra Debian i forkant av utgivelsen av <emphasis role=\"distribution\">Bul",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267861,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267861/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:42:06.468877+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige programmet har blitt fjernet fra Debian i forkant av utgivelsen av <emphasis role=\"distribution\">Bul",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige programmet har blitt fjernet fra Debian i forkant av utgivelsen av",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267860,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267860/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:42:04.799460+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige programmet har blitt fjernet fra Debian i forkant av utgivelsen av",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige programmet har blitt f",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267859,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267859/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:41:50.083878+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige programmet har blitt f",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige programmet h",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267857,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267857/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:41:48.079546+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige programmet h",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267856,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267856/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:41:46.440259+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det opprinnelige",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det op",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267855,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267855/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:41:45.052407+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, siden det op",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, si",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267853,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267853/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:41:43.216207+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pakken, si",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pak",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267852,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267852/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:41:41.633802+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4</emphasis>-pak",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267850,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267850/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:41:39.943472+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yum4",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yu",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267849,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267849/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:41:38.368817+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet, tilgjengelig som <command>yum4</command> i <emphasis role=\"pkg\">nextgen-yu",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267848,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267848/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:41:36.612798+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267847,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267847/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:41:22.016416+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>y",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267846,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267846/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:41:20.334138+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med <command>y",
            "old": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 20
            },
            "id": 35267845,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267845/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701173/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:41:18.610351+02:00",
            "action": 2,
            "target": "Hvis chroot er ment å kjøre Debian (eller et derivat derav), kan systemet bli igangsettes med <command>debootstrap</command>. Hvis det må installeres med et RPM-basert system (som f.eks. Fedora, CentOS, eller Scientific Linux), vil oppsettet måtte gjøres med",
            "old": "Hvis den virtuelle maskinen er ment til å kjøre en Debian (eller en av dens derivater), kan systemet bli initialisert med <command>debootstrap</command>, som beskrevet ovenfor. Men hvis den virtuelle maskinen skal monteres med et RPM-basert system (som Fedora, CentOS eller Scientific Linux), vil oppsettet måtte gjøres med <command>yum</command>-verktøyet (tilgjengelig i pakken med samme navn).",
            "details": {
                "state": 20,
                "source": "If a chroot is meant to run Debian (or one of its derivatives), the system can be initialized with <command>debootstrap</command>. But if it is to be installed with an RPM-based system (such as Fedora, CentOS or Scientific Linux), the setup will need to be done using the <command>yum</command> utility, available as <command>yum4</command> in the <emphasis role=\"pkg\">nextgen-yum4</emphasis> package, since the original program has been removed from Debian before the <emphasis role=\"distribution\">Bullseye</emphasis> release due to being unmaintained, outdated, and obsoleted by <command>dnf</command>.",
                "old_state": 10
            },
            "id": 35267843,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267843/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701138/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:38:16.040922+02:00",
            "action": 2,
            "target": "Disse oppføringene betyr, henholdsvis, at et virtuelt grensesnitt vil bli opprettet hver ny beholder; at det automatisk vil bli vist når det blir meldt at beholderen er startet; og at det automatisk vil bli koblet til <literal>lxcbr0</literal>-broen hos verten. Du vil finne diise innstillingene i den opprettede beholderens oppsett (<filename>/var/lib/lxc/testlxc/config</filename>), der også enhetens MAC-adresse vil være spesifisert i <literal>lxc.net.0.hwaddr</literal>. Skulle denne siste posten mangle eller være deaktivert, vil det genereres en tilfeldig MAC-adresse.",
            "old": "Disse oppføringene betyr, henholdsvis, at et virtuelt grensesnitt vil bli opprettet hver ny beholder; at det automatisk vil bli vist når det blir meldt at beholderen er startet; og at det automatisk vil bli koblet til <literal>lxcbr0</literal>-broen hos verten. Du vil finne diise innstillingene i den opprettede beholderens oppsett (<filename>/var/lib/lxc/testlxc/config</filename>), der også enhetens MAC-adresse vil være spesifisert i <literal>lxc.net.0.hwaddr. Skulle denne siste posten mangle eller være deaktivert, vil det genereres en tilfeldig MAC-adresse.",
            "details": {
                "state": 20,
                "source": "These entries mean, respectively, that a virtual interface will be created in every new container; that it will automatically be brought up when said container is started; and that it will be automatically connected to the <literal>lxcbr0</literal> bridge on the host. You will find these settings in the created container's configuration (<filename>/var/lib/lxc/testlxc/config</filename>), where also the device' MAC address will be specified in <literal>lxc.net.0.hwaddr</literal>. Should this last entry be missing or disabled, a random MAC address will be generated.",
                "old_state": 20
            },
            "id": 35267809,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267809/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701138/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:38:14.668215+02:00",
            "action": 2,
            "target": "Disse oppføringene betyr, henholdsvis, at et virtuelt grensesnitt vil bli opprettet hver ny beholder; at det automatisk vil bli vist når det blir meldt at beholderen er startet; og at det automatisk vil bli koblet til <literal>lxcbr0</literal>-broen hos verten. Du vil finne diise innstillingene i den opprettede beholderens oppsett (<filename>/var/lib/lxc/testlxc/config</filename>), der også enhetens MAC-adresse vil være spesifisert i <literal>lxc.net.0.hwaddr. Skulle denne siste posten mangle eller være deaktivert, vil det genereres en tilfeldig MAC-adresse.",
            "old": "Disse oppføringene betyr, henholdsvis, at et virtuelt grensesnitt vil bli opprettet hver ny beholder; at det automatisk vil bli vist når det blir meldt at beholderen er startet; og at det automatisk vil bli koblet til <literal>lxcbr0</literal>-broen hos verten. Du vil finne diise innstillingene i den opprettede beholderens oppsett (<filename>/var/lib/lxc/testlxc/config</filename>), der også enhetens MAC-adresse vil være spesifisert i <literal>lxc.. Skulle denne siste posten mangle eller være deaktivert, vil det genereres en tilfeldig MAC-adresse.",
            "details": {
                "state": 20,
                "source": "These entries mean, respectively, that a virtual interface will be created in every new container; that it will automatically be brought up when said container is started; and that it will be automatically connected to the <literal>lxcbr0</literal> bridge on the host. You will find these settings in the created container's configuration (<filename>/var/lib/lxc/testlxc/config</filename>), where also the device' MAC address will be specified in <literal>lxc.net.0.hwaddr</literal>. Should this last entry be missing or disabled, a random MAC address will be generated.",
                "old_state": 20
            },
            "id": 35267808,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267808/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701138/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:38:07.078610+02:00",
            "action": 2,
            "target": "Disse oppføringene betyr, henholdsvis, at et virtuelt grensesnitt vil bli opprettet hver ny beholder; at det automatisk vil bli vist når det blir meldt at beholderen er startet; og at det automatisk vil bli koblet til <literal>lxcbr0</literal>-broen hos verten. Du vil finne diise innstillingene i den opprettede beholderens oppsett (<filename>/var/lib/lxc/testlxc/config</filename>), der også enhetens MAC-adresse vil være spesifisert i <literal>lxc.. Skulle denne siste posten mangle eller være deaktivert, vil det genereres en tilfeldig MAC-adresse.",
            "old": "Disse oppføringene betyr, henholdsvis, at et virtuelt grensesnitt vil bli opprettet hver ny beholder; at det automatisk vil bli vist når det blir meldt at beholderen er startet; og at det automatisk vil bli koblet til <literal>lxcbr0</literal>-broen hos verten. Du vil finne diise innstillingene i den opprettede beholderens oppsett (<filename>/var/lib/lxc/testlxc/config</filename>), der også enhetens MAC-adresse vil være spesifisert i . Skulle denne siste posten mangle eller være deaktivert, vil det genereres en tilfeldig MAC-adresse.",
            "details": {
                "state": 20,
                "source": "These entries mean, respectively, that a virtual interface will be created in every new container; that it will automatically be brought up when said container is started; and that it will be automatically connected to the <literal>lxcbr0</literal> bridge on the host. You will find these settings in the created container's configuration (<filename>/var/lib/lxc/testlxc/config</filename>), where also the device' MAC address will be specified in <literal>lxc.net.0.hwaddr</literal>. Should this last entry be missing or disabled, a random MAC address will be generated.",
                "old_state": 20
            },
            "id": 35267806,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267806/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701138/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:38:05.111441+02:00",
            "action": 2,
            "target": "Disse oppføringene betyr, henholdsvis, at et virtuelt grensesnitt vil bli opprettet hver ny beholder; at det automatisk vil bli vist når det blir meldt at beholderen er startet; og at det automatisk vil bli koblet til <literal>lxcbr0</literal>-broen hos verten. Du vil finne diise innstillingene i den opprettede beholderens oppsett (<filename>/var/lib/lxc/testlxc/config</filename>), der også enhetens MAC-adresse vil være spesifisert i . Skulle denne siste posten mangle eller være deaktivert, vil det genereres en tilfeldig MAC-adresse.",
            "old": "Disse oppføringene betyr, henholdsvis, at et virtuelt grensesnitt vil bli opprettet hver ny beholder; at det automatisk vil bli vist når det blir meldt at beholderen er startet; og at det automatisk vil bli koblet til <literal>lxcbr0</literal>-broen hos verten. Du vil finne diise innstillingene i den opprettede beholderens oppsett (<filename>/var/lib/lxc/testlxc/config</filename>) og at MAC-adressen vil være som spesifisert. Skulle denne siste posten mangle eller være deaktivert, vil det genereres en tilfeldig MAC-adresse.",
            "details": {
                "state": 20,
                "source": "These entries mean, respectively, that a virtual interface will be created in every new container; that it will automatically be brought up when said container is started; and that it will be automatically connected to the <literal>lxcbr0</literal> bridge on the host. You will find these settings in the created container's configuration (<filename>/var/lib/lxc/testlxc/config</filename>), where also the device' MAC address will be specified in <literal>lxc.net.0.hwaddr</literal>. Should this last entry be missing or disabled, a random MAC address will be generated.",
                "old_state": 20
            },
            "id": 35267805,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267805/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701138/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:37:44.962860+02:00",
            "action": 2,
            "target": "Disse oppføringene betyr, henholdsvis, at et virtuelt grensesnitt vil bli opprettet hver ny beholder; at det automatisk vil bli vist når det blir meldt at beholderen er startet; og at det automatisk vil bli koblet til <literal>lxcbr0</literal>-broen hos verten. Du vil finne diise innstillingene i den opprettede beholderens oppsett (<filename>/var/lib/lxc/testlxc/config</filename>) og at MAC-adressen vil være som spesifisert. Skulle denne siste posten mangle eller være deaktivert, vil det genereres en tilfeldig MAC-adresse.",
            "old": "Disse oppføringene betyr, henholdsvis, at et virtuelt grensesnitt vil bli opprettet hver ny beholder; at det automatisk vil bli vist når det blir meldt at beholderen er startet; og at det automatisk vil bli koblet til <literal>lxcbr0</literal>-broen hos verten. Du vil finne diise innstillingene i den opprettede beholderens oppsett (<filename>/var/lib/lxc/testlxc/config og at MAC-adressen vil være som spesifisert. Skulle denne siste posten mangle eller være deaktivert, vil det genereres en tilfeldig MAC-adresse.",
            "details": {
                "state": 20,
                "source": "These entries mean, respectively, that a virtual interface will be created in every new container; that it will automatically be brought up when said container is started; and that it will be automatically connected to the <literal>lxcbr0</literal> bridge on the host. You will find these settings in the created container's configuration (<filename>/var/lib/lxc/testlxc/config</filename>), where also the device' MAC address will be specified in <literal>lxc.net.0.hwaddr</literal>. Should this last entry be missing or disabled, a random MAC address will be generated.",
                "old_state": 20
            },
            "id": 35267802,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267802/?format=api"
        },
        {
            "unit": "https://hosted.weblate.org/api/units/82701138/?format=api",
            "component": "https://hosted.weblate.org/api/components/debian-handbook/12_advanced-administration/?format=api",
            "translation": "https://hosted.weblate.org/api/translations/debian-handbook/12_advanced-administration/nb_NO/?format=api",
            "user": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "author": "https://hosted.weblate.org/api/users/kingu/?format=api",
            "timestamp": "2022-09-26T16:37:42.605404+02:00",
            "action": 2,
            "target": "Disse oppføringene betyr, henholdsvis, at et virtuelt grensesnitt vil bli opprettet hver ny beholder; at det automatisk vil bli vist når det blir meldt at beholderen er startet; og at det automatisk vil bli koblet til <literal>lxcbr0</literal>-broen hos verten. Du vil finne diise innstillingene i den opprettede beholderens oppsett (<filename>/var/lib/lxc/testlxc/config og at MAC-adressen vil være som spesifisert. Skulle denne siste posten mangle eller være deaktivert, vil det genereres en tilfeldig MAC-adresse.",
            "old": "Disse oppføringene betyr, henholdsvis, at et virtuelt grensesnitt vil bli opprettet hver ny beholder; at det automatisk vil bli vist når det blir meldt at beholderen er startet; og at det automatisk vil bli koblet til <literal>lxcbr0</literal>-broen hos verten. Du vil finne diise innstillingene i den opprettede beholderens oppsett (<filename>/var/ og at MAC-adressen vil være som spesifisert. Skulle denne siste posten mangle eller være deaktivert, vil det genereres en tilfeldig MAC-adresse.",
            "details": {
                "state": 20,
                "source": "These entries mean, respectively, that a virtual interface will be created in every new container; that it will automatically be brought up when said container is started; and that it will be automatically connected to the <literal>lxcbr0</literal> bridge on the host. You will find these settings in the created container's configuration (<filename>/var/lib/lxc/testlxc/config</filename>), where also the device' MAC address will be specified in <literal>lxc.net.0.hwaddr</literal>. Should this last entry be missing or disabled, a random MAC address will be generated.",
                "old_state": 20
            },
            "id": 35267801,
            "action_name": "Translation changed",
            "url": "https://hosted.weblate.org/api/changes/35267801/?format=api"
        }
    ]
}