I've been trying to update my system that contains the Network Manager Applet (as I am on XFCE), but I am running into the following error after my databases/mirrors are updated: 
:: Starting full system upgrade...
warning: lib32-p11-kit: local (0.24.1-1) is newer than obmultilib (0.24.0-2)
resolving dependencies...
warning: ignoring package systemd-252.1-1
warning: cannot resolve "systemd", a dependency of "gcr-4"
warning: cannot resolve "gcr-4", a dependency of "libnma-common"
warning: cannot resolve "libnma-common=1.10.4-3", a dependency of "libnma"
warning: ignoring package systemd-252.1-1
warning: cannot resolve "systemd", a dependency of "gcr-4"
warning: cannot resolve "gcr-4", a dependency of "libnma-common"
warning: ignoring package systemd-252.1-1
warning: cannot resolve "systemd", a dependency of "gcr-4"
warning: cannot resolve "gcr-4", a dependency of "libnma-common"
warning: cannot resolve "libnma-common=1.10.4-3", a dependency of "libnma"
warning: ignoring package systemd-252.1-1
warning: cannot resolve "systemd", a dependency of "gcr-4"
warning: cannot resolve "gcr-4", a dependency of "libnma-common"
warning: cannot resolve "libnma-common=1.10.4-3", a dependency of "libnma"
:: The following packages cannot be upgraded due to unresolvable dependencies:
      libnma  libnma-common
Ignoring the above, and proceeding with the update anyway got me the below: 
error: failed to commit transaction (conflicting files)
network-manager-applet: /usr/share/glib-2.0/schemas/org.gnome.nm-applet.gschema.xml exists in filesystem (owned by libnma-common)
Errors occurred, no packages were upgraded.
 -> error installing repo packages
A quick search has determined that the above can be rectified if libnma & libnma-common are also up-to-date. However, that is no longer possible as they now pull in systemd.

I'm not technically confident enough to deal with the potential complications that may arise if I just ignore the 2 packages alone and do a partial upgrade with the others, so I have left it as it is.

Is there some workaround? Thank you in advance!
I think the real issue is gcr-4 which annoyingly got added as a dependency recently to the libnma packages and pulls in systemd (whereas the original gcr package doesn't).

The systemd dependency for gcr-4 isn't really major. So you should be able to install gcr-4 this way: 
# pacman -Sy gcr-4 --assume-installed=systemd
It'll install, but you'll get an error - which you can ignore - b/c it's trying to install and activate a systemd service file for gcr-ssh-agent: 
/tmp/[...]/.INSTALL: line 3: systemctl: command not found
error: command failed to execute correctly
You should then be able to update libnma and libnma-common without any issues. But I'm assuming you have a way to rollback your system if something goes wrong or you use something like downgrade from the AUR to revert specific packages.

BTW, I noticed you have the arch version of lib32-p11-kit installed for some reason (which does depend on lib32-systemd) rather the obarun version. Hopefully Eric can update that soon.
Thanks for the tip!

I do have Timeshift backups, but since I depend on my computer for work, I'll probably try this out in the weekends. Hopefully some other updates may emerge in the meanwhile.

As for "lib32-p11-kit", I believe it was pulled in before I enabled Obarun's multilib repo. Once Obarun's multilib is up-to-date, would it be automatically replaced?
Thanks for the feedback.
Please synchronize Obarun repo and retry to update it then tell us.
Hyperspace wroteThanks for the tip!

I do have Timeshift backups, but since I depend on my computer for work, I'll probably try this out in the weekends. Hopefully some other updates may emerge in the meanwhile.

As for "lib32-p11-kit", I believe it was pulled in before I enabled Obarun's multilib repo. Once Obarun's multilib is up-to-date, would it be automatically replaced?
Now that Eric has built an Obarun version of gcr-4, you can completely ignore my tip. (Thanks, Eric!)

As for lib32-p11-kit, once it gets updated in the Obarun multib repo, yes, it'll automatically get replaced when you update your packages. Typically, an Obarun version will have a pkgrel verison # +1 over the comparable Arch version, so the Obarun lib32-pk11-kit will be 0.24.1-2 when it gets updated.
I decided to update anyway (with a Timeshift created just before), and can confirm that everything went smoothly. No perceivable issues with my system so far.

Thank you for your herculean efforts in purifying systemd out of our systems!

Powered by Obarun