Created attachment 950988 [details] install and config logs Description of problem: Packstack on Fedora 21 fails w/ [1;31mError: Execution of '/usr/bin/yum -d 0 -e 0 -y install scsi-target-utils' returned 1: Delta RPMs disabled because /usr/bin/applydeltarpm not installed. [0;36mDebug: Executing '/usr/bin/yum -d 0 -e 0 -y install openstack-cinder'[0m [1;31mError: Execution of '/usr/bin/yum -d 0 -e 0 -y install openstack-cinder' returned 1: Transaction check error: file /etc/inittab from install of systemd-216-5.fc21.x86_64 conflicts with file from package initscripts-9.55-2.fc21.x86_64 file /etc/sysctl.conf from install of systemd-216-5.fc21.x86_64 conflicts with file from package initscripts-9.55-2.fc21.x86_64 Error Summary -------------[0m [1;31mError: /Stage[main]/Cinder/Package[cinder]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install openstack-cinder' returned 1: Transaction check error: file /etc/inittab from install of systemd-216-5.fc21.x86_64 conflicts with file from package initscripts-9.55-2.fc21.x86_64 file /etc/sysctl.conf from install of systemd-216-5.fc21.x86_64 conflicts with file from package initscripts-9.55-2.fc21.x86_64 Error Summary see attached logs and config details
*** Bug 1159979 has been marked as a duplicate of this bug. ***
yum -y update of f21 resolved this issue..
> yum -y update of f21 resolved this issue.. What got updated? rpm -q systemd initscripts
Transaction check error: file /etc/inittab from install of systemd-216-12.fc21.x86_64 conflicts with file from package initscripts-9.54-5.fc21.x86_64 file /etc/sysctl.conf from install of systemd-216-12.fc21.x86_64 conflicts with file from package initscripts-9.54-5.fc21.x86_64 ERROR: Command failed. See logs for output. # /usr/bin/yum-builddep --installroot /var/lib/mock/fedora-21-x86_64/root/ --releasever 21 /var/lib/mock/fedora-21-x86_64/root//builddir/build/SRPMS/azureus-5.5.0.0-2.fc21.src.rpm
rpm -q initscripts systemd with : initscripts-9.56.1-6.fc21.x86_64 systemd-216-20.fc21.x86_6 this bug is fixed , may we close this bug with resolved -> current release ?