You are not logged in.
When I -Syu'ed this morning, iptables, nftables, etc. upgraded and a bunch of post-install hooks failed with messages like:
[2019-06-21 07:06] [ALPM] running 'systemd-binfmt.hook'...
[2019-06-21 07:06] [ALPM-SCRIPTLET] /usr/lib/systemd/systemd-binfmt: error while loading shared libraries: libip4tc.so.0: cannot open shared object file: No such file or directory
[2019-06-21 07:06] [ALPM] running 'systemd-daemon-reload.hook'...
[2019-06-21 07:06] [ALPM-SCRIPTLET] /usr/bin/systemctl: error while loading shared libraries: libip4tc.so.0: cannot open shared object file: No such file or directory
[2019-06-21 07:06] [ALPM] running 'systemd-sysusers.hook'...
[2019-06-21 07:06] [ALPM-SCRIPTLET] /usr/bin/systemd-sysusers: error while loading shared libraries: libip4tc.so.0: cannot open shared object file: No such file or directory
[2019-06-21 07:06] [ALPM] running 'systemd-tmpfiles.hook'...
[2019-06-21 07:06] [ALPM-SCRIPTLET] /usr/bin/systemd-tmpfiles: error while loading shared libraries: libip4tc.so.0: cannot open shared object file: No such file or directory
the file /usr/lib/libip4tc.so.0 is missing, hence the errors, I suppose. Is this serious? Is this a bug in one of the packages?
Last edited by fiddlinmacx (2019-06-21 14:42:43)
Offline
Either you have a broken mirror or you are doing partial upgrades as systemd was updated at the same time as iptables. But you have a new version of iptables with an (apparently) stale version of systemd.
What's the output of `pacman -Q systemd`?
Last edited by Trilby (2019-06-21 12:26:58)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
Quite right. Thanks. It was a stale systemd that I didn't notice. I sometimes --ignore some things so I don't have to reboot but I should have watched more closely. Mischief managed.
Offline
Doing partial upgrades has nothing to do with needing to reboot.
If you are concerned about kernel modules, you can ensure any you need are loaded before upgrading the kernel, or you can hold/ignore the kernel. That's about the only safe package to hold back (certainly the only one in [core] or the base group that is safe to hold back). But doing a partial upgrade and holding back systemd while upgrading everything else is a recipe for catastrophic breakage.
Change that habbit.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
I will. Thanks.
Offline