Description:
I made an update, like always, but this time, and again, Arch package repository update first the libidn2, which broke systemd completely after rebooting, because the 'libidn2.so.0' was not present. I didn't upgrade the systemd because of issue with Docker (https://github.com/docker/for-linux/issues/552) and systemd (read changelog of 240 version).

I decided then to downgrade 'libidn2' manually, by booting with USB to the 2.0 version but that break pacman so only 'xz' helped to upgrade 'libidn2' to the previous version (2.1).

Is maybe a better way to 'not break package compatibility'?
Maybe would be nice to have a system which checks the /*/lib folders (and maybe bin) for changes (eg: file names) (compares current and the new package) and notifies about the possible issues?

Missing 'libidn2.so.0' screenshot & Kernel panic because of systemd:
(Tweet: https://twitter.com/TheAifam5/status/1085264977051693058)

PS. I set that issue to critical, because there was no info about the 'breakage' of the system after the 'libidn2' package. If you don't agree, please change it to the proper level.

Regards,
Mateusz Paluszkiewicz