Description of problem: When trying to remove abrt from installed system you end up removing dracut-network in the process due to dependency's # rpm -q --whatrequires dracut-network kexec-tools-2.0.10-4.fc23.x86_64 # rpm -q --whatrequires kexec-tools abrt-addon-vmcore-2.7.1-1.fc23.x86_64 Should not the kdump dracut modules that reside in kexec-tools be packed as a separated sub component of dracut? Is there any particular reason why dracut is not packaging each of it's modules in a separated sub component of dracut ( dracut-module-$FOO )? Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. dnf remove abrt 2. rpm -q --whatrequires dracut-network 3. rpm -q --whatrequires kexec-tools Actual results: Removing abrt removes dracut-networkd Expected results: removal of uncessary junk like abrt should not result in removal of core component like initrd in the distribution Additional info:
kexec-tools needs/wants dracut-network if the kdump target is on network. IMHO, this dependency is bogus anyway. The real problem here, though, is that dnf removes leaves, which are not needed anymore automatically. So, abrt-addon-vmcore requires kexec-tools, which requires dracut-network. Because nothing else requires dracut-network, dnf thinks it can remove dracut-network, too. Reassigning to dnf.
*** This bug has been marked as a duplicate of bug 1259865 ***
(In reply to Jan Silhan from comment #2) > > *** This bug has been marked as a duplicate of bug 1259865 *** Can you explain how this relates to packagekit since I dont use packagekit to install update components, which this the link bug seems to be about?