On Wed, Jul 1, 2015 at 3:52 PM, <jmcf125@xxxxxxxxxxxxxxx> wrote: > However, in the latest update it seems an awful lot of packages I use > suddenly require systemd. First, I have a conflict between libgudev and > eudev-systemdcompat, so the installation stops right there. I don't even > remember a libgudev package when I used systemd! The pacman output, 1st > refusing to remove eudev, then accepting, is as follows: libgudev was split from systemd into its own project. As a result, some packages have picked up a dependency on libgudev. However, libgudev cannot be installed on your system because it conflicts with eudev. To clear up your dependencies, try having whatever eudev package contains libgudev.so provide libgudev.
