You are not logged in.
- Topics: Active | Unanswered
#1 2013-01-08 11:29:03
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 13,049
systemd-197-1 : rc-local.service exists in filesystem
pacman -Syu
:: Synchronizing package databases...
testing is up to date
core is up to date
extra is up to date
community is up to date
multilib-testing is up to date
multilib is up to date
LoneVVolf is up to date
:: Starting full system upgrade...
:: Replace nss-myhostname with testing/systemd? [Y/n]
resolving dependencies...
looking for inter-conflicts...
Targets (3): nss-myhostname-0.3-3 [removal] pango-1.32.5-1 systemd-197-1
Total Installed Size: 15.93 MiB
Net Upgrade Size: -0.41 MiB
Proceed with installation? [Y/n]
(2/2) checking package integrity [####################################################################] 100%
(2/2) loading package files [####################################################################] 100%
(2/2) checking for file conflicts [####################################################################] 100%
error: failed to commit transaction (conflicting files)
systemd: /usr/lib/systemd/system/rc-local.service exists in filesystem
Errors occurred, no packages were upgraded.pacman -Qo /usr/lib/systemd/system/rc-local.service
/usr/lib/systemd/system/rc-local.service is owned by initscripts 2012.10.1-1I know how to solve this, (remove initscripts & switch to sysv-compat) , but wanted to alert other [testing] users about this conflict.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
#3 2013-01-08 12:03:20
- Lone_Wolf
- Administrator
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 13,049
Re: systemd-197-1 : rc-local.service exists in filesystem
another user already created a bug report : Bug 33333
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline