You are not logged in.
So I just want to confirm that sysvinit-tools is replacing systemd-sysvinit and that I can safely remove systemd-sysvinit before doing an upgrade that will install sysvinit-tools as a dependency.
Pacman failed to upgrade, telling me that /usr/bin/wall, /usr/bin/last{,b} exist in the filesystem. I determined that these files were owned by systemd-sysvinit, so my plan is to remove that and then proceed with the install. Is this the recommended procedure?
Last edited by WonderWoofy (2012-09-01 22:34:27)
Offline
Offline
So I just want to confirm that sysvinit-tools is replacing systemd-sysvinit and that I can safely remove systemd-sysvinit before doing an upgrade that will install sysvinit-tools as a dependency.
That's right. I added a note to the AUR comments.
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |
Offline
This seems to be a different issue... I understand that in order to do away with initscripts, it is recommended to install systemd-sysvcompat. But I had installed systemd-sysvinit which replaced certain functions like pidof and last. So that package was conflicting with a the new dependency sysvinit-tools.
@progandy - thanks, that is the info I was looking for.... installation went without a hitch after removal.
Offline
Glad you got it, WW.
Offline
Thanks graysky, I appreciate your intentions with those links BTW.
Offline