Arch Linux

greengold

Member

Registered: 2010-01-30

Posts: 199

[SOLVED] not installed package in conflict

Hi all,
I just tried to update packages from AUR after some time and I got this strange (for me) conflict:

$pacaur -Suy
   ...
:: eudev-systemdcompat and libsystemd are in conflict (libsystemd). Remove libsystemd? [y/N]

the strange aspect is that I don't have 'eudev-systemdcompat' installed:

$ pacaur -Qi eudev-systemdcompat
error: package 'eudev-systemdcompat' was not found

What is going on and how do I resolve it? Personally I don't see a reason for replacing systemd, I just want to update AUR stuff.

Last edited by greengold (2015-11-08 13:07:30)

mauritiusdadd

Member

From: Benevento, Italy

Registered: 2013-10-27

Posts: 776

Re: [SOLVED] not installed package in conflict

Maybe one of your AUR packages is pulling eudev-systemdcompat as dependency, you have just to find which one (the only one that seems to depend directly on it is upower-pm-utils).

Last edited by mauritiusdadd (2015-11-08 11:53:29)

---

About me - github

-- When you have eliminated the impossible, whatever remains, however improbable, must be the truth -- Spock | Sherlock Holmes

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 13,648

Website

Re: [SOLVED] not installed package in conflict

I'm not familiar with pacaur, but I recommend that you update your AUR packages manually, one-by-one, until you find the one that wants to pull in this new package.

Moving to AUR issues.

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

greengold

Member

Registered: 2010-01-30

Posts: 199

Re: [SOLVED] not installed package in conflict

Maybe one of your AUR packages is pulling eudev-systemdcompat as dependency, you have just to find which one (the only one that seems to depend directly on it is upower-pm-utils).

that was right. 'desktop-privileges' package was pulling it. Resolved upon removal.
Thanks!