install issues in containers

[Christian Ehrhardt ]

Hi,
by accident (fortunately?) I ran into this after some testing for getting this promoted to main which seemed fine.

But later on in the container I had it installed I got issues and wanted to report them so they can be fixed before 20.04 releases as I'll assume it will then be default installed as part of fwupd dependencies.

What happens (to me at least) is that on re-install it hits this:

Setting up tpm-udev (0.2) ...
Failed to send reload request: No such file or directory
Failed to write 'change' to '/sys/devices/platform/STM7304:00/tpm/tpm0/uevent': Read-only file system
Failed to write 'add' to '/sys/devices/platform/STM7304:00/tpm/tpm0/uevent': Read-only file system
dpkg: error processing package tpm-udev (--configure):
 installed tpm-udev package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 tpm-udev
E: Sub-process /usr/bin/dpkg returned an error code (1)

-x identified this is from the udevadm interaction
+ udevadm control --reload-rules
Failed to send reload request: No such file or directory
+ :
+ udevadm trigger --sysname-match=tpm[0-9]*
Failed to write 'change' to '/sys/devices/platform/STM7304:00/tpm/tpm0/uevent': Read-only file system
+ :
+ udevadm trigger --action=add --subsystem-match=tpm
Failed to write 'add' to '/sys/devices/platform/STM7304:00/tpm/tpm0/uevent': Read-only file system

You should guard against the issue with pre-checks or consider letting it continue gracefully if that seems better to you.

[Christian Ehrhardt  (paelzer)]

At:
if udevadm --version > /dev/null; then
    udevadm control --reload-rules

Maybe make the reload also a check.
If it fails do not go any further as it implies here udev has some general issue out of control of your package and the next commands would fail for sure.

[Mario Limonciello (superm1)]

Fixed in 0.3 release.