plasma-workspace-5.20.1.1-1.1 cannot be installed with:
...
plasma-workspace: /usr/share/locale/zh_TW/LC_MESSAGES/kfontinst.mo exists in filesystem (owned by plasma-desktop)
plasma-workspace: /usr/share/locale/zh_TW/LC_MESSAGES/krdb.mo exists in filesystem (owned by plasma-desktop)
plasma-workspace: /usr/share/polkit-1/actions/org.kde.fontinst.policy exists in filesystem (owned by plasma-desktop)
use this to overwrite those duplicate files:
pacman -Sy --overwrite='*' plasma-workspace
The libtraceevent package prior to version 5.9-1 was missing a soname link. This has been fixed in 5.9-1, so the upgrade will need to overwrite the untracked files created by ldconfig. If you get any of these errors
libtraceevent: /usr/lib/libtraceevent.so.1 exists in filesystem
when updating, use
pacman -Syu --overwrite /usr/lib/libtraceevent.so.1
to perform the upgrade.
The ghostpcl and ghostxps packages prior to version 9.53.2-2 were missing a soname link each. This has been fixed in 9.53.2-2, so the upgrade will need to overwrite the untracked files created by ldconfig. If you get any of these errors
ghostpcl: /usr/lib/libgpcl6.so.9 exists in filesystem
ghostxps: /usr/lib/libgxps.so.9 exists in filesystem
when updating, use
pacman -Syu --overwrite /usr/lib/libgpcl6.so.9,/usr/lib/libgxps.so.9
to perform the upgrade.
a change was made this week to 'nonsystemd/base', in order to reduce dependency conflicts, when installing a nonsystemd system, and when migrating to or from nonsystemd<->systemd - this has exposed several dependency conflicts which were not obvious before, and made them explicit
manual intervention will be required, if pacman has a conflict such as:
your-initfreedom and systemd-_ANYTHING_ are in conflict
if you get that error, see this redmine issue for the solution:
https://labs.parabola.nu/issues/2884
there is a separate, but related issue, where we are collecting examples of conflicts which were exposed by this change to ...
if you have a USB wifi device which uses the ath9k or ath9k_htc kernel module, you should postpone upgrading to any of the 5.7.6 kernels; or the device may not work when you next reboot - PCI devices do not seem to be affected by this bug
watch this bug report for further details
linux-libre and linux-libre-headers 5.7.6 have been pulled from the repos and replaced with 5.7.2; but other kernels remain at 5.7.6 - if you have already upgraded to one of the 5.7.6 kernels, and your wifi does not work ...