Bug #2884

Packaging Request #2506: arch introduced a base metapackage to replace the meta group

Housekeeping #2549: move non-systemd packages to [nonsystemd]

Bug #2576: [openrc-desktop] rearrange openrc groups

Bug #2886: systemd and openrc are in conflict (systemd-tools)

your-initfreedom and systemd-nss-myhostname are in conflict

infinite_recursion - over 3 years ago - . Updated almost 3 years ago.

% Done:



# pacman -Syu
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: your-initfreedom and systemd-nss-myhostname are in conflict

While updating, above error show up, cannot update.



Updated by bill-auger over 3 years ago

  • Status changed from unconfirmed to confirmed
if pacman has a conflict such as: "your-initfreedom and systemd-_ANYTHING_ are in conflict", manual intervention will be required - the reason for this is that, before this week, 'nonsystemd/base' did not actually conflict with any systemd packages - in some cases, depending on how the initial install was done, some systemd packages would be installed, even on non-systemd systems - those packages not actually needed though; and some people would complain about them - the separation was made to be more strict by adding 'your-initfreedom' to 'nonsystemd/base'; which conflicts directly with those systemd packages - if your system in in that state, those systemd packages need to be uninstalled manually now - it is most likely these four:
  • systemd-nss-myhostname
  • systemd-nss-mymachines
  • systemd-nss-resolve
  • systemd-nss-systemd

this command will list which systemd packages that you have installed:

$ pacman -Ss systemd | grep -E 'libre/systemd.*\[installed'

this command will uninstall every package with a name beginning with: 'systemd':

$ sudo pacman -R $(pacman -Ss systemd | grep -E 'libre/systemd.*\[installed' | sed 's|libre/\([^ ]*\) .*|\1|')

finally, do a strict sync with the [nonsystemd] repo:

$ sudo pacman -Syyuu

if you get another conflict which mentions 'netctl', then uninstall 'netctl' and 'parabola-base' also

$ sudo pacman -R netctl parabola-base
$ sudo pacman -Syyuu

Updated by bill-auger over 3 years ago

  • Priority changed from bug to discussion
  • Description updated (diff)

Updated by infinite_recursion over 3 years ago

Removed those 4, now it conflicts with systemd-resolvconf

:: removing systemd-resolvconf breaks dependency 'resolvconf' required by netctl

Updated by bill-auger over 3 years ago

$ sudo pacman -R netctl parabola-base


Updated by infinite_recursion over 3 years ago

:: removing netctl breaks dependency 'netctl' required by parabola-base

Updated by Megver83 over 3 years ago

netctl is made for systemd, remove it with parabola-base too, you don't need them; parabola-base packages can be easily installed by hand (if you need them). E.g. I don't have dhcpcd (I use NM), mc, vi, and maybe others from that meta package.


Updated by infinite_recursion over 3 years ago

Yes that did it

Go to another virtual terminal and login

pacman -R parabola-base
pacman -R netctl
pacman -R systemd-nss-myhostname systemd-nss-mymachines systemd-nss-resolve systemd-nss-systemd systemd-resolvconf
pacman -Syu

This solves the problem. Thanks guys!


Updated by bill-auger over 3 years ago

  • Parent task set to #2886

Updated by Time4Tea about 3 years ago

I seem to be having a problem that relates to this: I am trying to upgrade and lib32-systemd is conflicting with your-initfreedom. Unfortunately, lib32-systemd (which I disn't have installed previously) seems to be a dependency of lib32-dbus, which is in turn required for quite a few 'lib32' packages. This dependency of lib32-dbus on systemd seems to be relatively new. It didn't use to require it.

Anyway, for now I will just remove parabola-base and not have your-initfreedom installed.


Updated by bill-auger almost 3 years ago

libre/parabola-base can not be installed with nonsystemd - there
needs to be an analogous nonsystemd/parabola-base; but it doesnt
exist yet

Also available in: Atom PDF