14ab6e9 rpm: when disabling a unit, do not complain if systemd is not running

Authored and Committed by zbyszek 3 years ago
    rpm: when disabling a unit, do not complain if systemd is not running
    
    $ sudo dnf remove --installroot=/var/tmp/img1 systemd-networkd
    ...
      Running scriptlet: systemd-networkd-248~rc4-4.fc32.x86_64      1/1
    Removed /etc/systemd/system/multi-user.target.wants/systemd-networkd.service.
    Removed /etc/systemd/system/sockets.target.wants/systemd-networkd.socket.
    Removed /etc/systemd/system/dbus-org.freedesktop.network1.service.
    Removed /etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service.
    System has not been booted with systemd as init system (PID 1). Can't operate.
    Failed to connect to bus: Host is down
    
    (Another option would be make --now do nothing if systemd is not running.
    But I think that's not too good. 'disable --now' doing nothing would be OK,
    since if systemd is not running, the service is not running either, so we are
    in the desired state. But that argument doesn't work for 'enable --now'. And
    accepting 'disable --now' but not 'enable --now' seems overly complex. So I
    think it is better to make the scriptlet handle this case explicitly.)
    
    Also, let's reindent the file to 4 spaces. Very deeply nested scriptlets are
    harder to read, and the triggers file is indented to 4 spaces already.
    
    (cherry picked from commit a59eb7d78f2f7aea0524b4f16cbb0fe3ef1b9aac)
    
        
file modified
+14 -10