I guess we’ve found the “bug” with removing foreign packages before doing an update. A package may become foreign if it is removed from the repos and replaced by another package (in this case, kdsoap-qt6 was removed from the repos & replaced by kdsoap):
The change happened automatically on my Testing branch system in last week’s update:
paclog --grep=kdsoap
[2023-11-13T14:31:01+1100] [ALPM] removed kdsoap (2.1.1-1)
[2023-11-13T14:31:01+1100] [ALPM] installed kdsoap-qt5 (2.1.1-2)
[2023-11-13T14:31:04+1100] [ALPM] installed kdsoap-qt6 (2.1.1-2)
[2023-11-13T14:31:04+1100] [ALPM] upgraded kdsoap-ws-discovery-client (git20200927-2 -> 0.3.0-2)
[2024-01-13T13:30:38+1100] [ALPM] upgraded kdsoap-qt5 (2.1.1-2 -> 2.2.0-1)
[2024-01-13T13:30:38+1100] [ALPM] upgraded kdsoap-qt6 (2.1.1-2 -> 2.2.0-1)
[2024-03-06T20:38:01+1100] [ALPM] upgraded kdsoap-ws-discovery-client (0.3.0-2 -> 0.4.0-1)
[2024-05-19T10:27:20+1000] [ALPM] removed kdsoap-qt5 (2.2.0-1)
[2025-11-06T19:09:39+1100] [ALPM] upgraded kdsoap-ws-discovery-client (0.4.0-1 -> 0.4.0-2)
[2026-03-17T08:15:53+1100] [ALPM] removed kdsoap-qt6 (2.2.0-1)
[2026-03-17T08:16:01+1100] [ALPM] installed kdsoap (2.3.0-1)
[2026-03-17T08:16:01+1100] [ALPM] upgraded kdsoap-ws-discovery-client (0.4.0-2 -> 0.4.0-3)
I’ve found that best practice is to just update the system packages first (sudo pacman -Syu or pamac update --no-aur).
After that is done, foreign packages can then be updated/removed/checked etc.
Attempting to remove system packages that have been removed from the repos or renamed before their replacements have been installed via the system update can cause dependency issues.