4:43 p.m.
Hullo
I’m sure that I’m being a bit dim here and that I’ve seen this working. However.
Starting with a downloaded image for a Pi (3b+), after a `rpm-ostree upgrade`, I seem
unable to deploy layered packages. They seem to install, but after the reboot, they’re not
there. As an example, I tried to drop `toolbox` onto the image so that I could build some
of my own rpms to run under systemd, using the approach here: https://bit.ly/3b8Ivri. The
initial status before installation looks like this:
```
rpm-ostree status
State: idle
Deployments:
* ostree://fedora-iot:fedora/stable/aarch64/iot
Version: 32.20200817.0 (2020-08-17T15:28:18Z)
Commit:
ace3685f47d39f5d4b6065d49554cf9ada92da685541640298b53576895176ea
GPGSignature: Valid signature by 97A1AE57C3A2372CCA3A4ABA6C13026D12C944D0
ostree://fedora-iot:fedora/stable/aarch64/iot
Version: 32.20200603.0 (2020-06-03T10:45:43Z)
Commit:
c02bd26925b4e849fd0e53f3645e97b5cb22f47d7614c5a047d6200c64b3421b
GPGSignature: Valid signature by 7D22D5867F2A4236474BF7B850CB390B3C3359C4
```
`sudo rpm-ostree install toolbox` progresses as I’d expect, creating a new bootable
deployment:
```
[tim@localhost ~]$ sudo rpm-ostree install toolbox
Checking out tree ace3685... done
Enabled rpm-md repositories: fedora-cisco-openh264 updates fedora fedora-modular
updates-modular
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2020-03-17T20:10:43Z
rpm-md repo 'updates' (cached); generated: 2020-08-27T14:18:53Z
rpm-md repo 'fedora' (cached); generated: 2020-04-22T22:22:16Z
rpm-md repo 'fedora-modular' (cached); generated: 2020-04-22T20:58:40Z
rpm-md repo 'updates-modular' (cached); generated: 2020-08-27T14:52:01Z
Importing rpm-md... done
Resolving dependencies... done
Checking out packages... done
Running pre scripts... done
Running post scripts... done
Running posttrans scripts... done
Writing rpmdb... done
Writing OSTree commit... done
⠉ Staging deployment...
Staging deployment... done
Freed: 354.4?MB (pkgcache branches: 217)
Added:
flatpak-session-helper-1.6.5-1.fc32.aarch64
toolbox-0.0.93-1.fc32.aarch64
Run "systemctl reboot" to start a reboot
```
and the status looks ok (ignoring the niggling error):
```
[tim@localhost ~]$ rpm-ostree status
error: Timeout was reached
[tim@localhost ~]$ rpm-ostree status
State: idle
Deployments:
ostree://fedora-iot:fedora/stable/aarch64/iot
Version: 32.20200817.0 (2020-08-17T15:28:18Z)
BaseCommit:
ace3685f47d39f5d4b6065d49554cf9ada92da685541640298b53576895176ea
GPGSignature: Valid signature by 97A1AE57C3A2372CCA3A4ABA6C13026D12C944D0
Diff: 2 added
LayeredPackages: toolbox
* ostree://fedora-iot:fedora/stable/aarch64/iot
Version: 32.20200817.0 (2020-08-17T15:28:18Z)
Commit:
ace3685f47d39f5d4b6065d49554cf9ada92da685541640298b53576895176ea
GPGSignature: Valid signature by 97A1AE57C3A2372CCA3A4ABA6C13026D12C944D0
ostree://fedora-iot:fedora/stable/aarch64/iot
Version: 32.20200603.0 (2020-06-03T10:45:43Z)
Commit:
c02bd26925b4e849fd0e53f3645e97b5cb22f47d7614c5a047d6200c64b3421b
GPGSignature: Valid signature by 7D22D5867F2A4236474BF7B850CB390B3C3359C4
```
But when I reboot, that deployment isn’t the image used and it’s disappeared from
rpm-ostree’s world:
```
[tim@localhost ~]$ sudo rpm-ostree status
State: idle
Deployments:
* ostree://fedora-iot:fedora/stable/aarch64/iot
Version: 32.20200817.0 (2020-08-17T15:28:18Z)
Commit:
ace3685f47d39f5d4b6065d49554cf9ada92da685541640298b53576895176ea
GPGSignature: Valid signature by 97A1AE57C3A2372CCA3A4ABA6C13026D12C944D0
ostree://fedora-iot:fedora/stable/aarch64/iot
Version: 32.20200603.0 (2020-06-03T10:45:43Z)
Commit:
c02bd26925b4e849fd0e53f3645e97b5cb22f47d7614c5a047d6200c64b3421b
GPGSignature: Valid signature by 7D22D5867F2A4236474BF7B850CB390B3C3359C4
```
Did I forget how this type of layered installation should work?
Tim