Description of problem: Doing 'dnf update' on a machine without any encrypted partitions (and thus no /etc/crypttab), I see: ... Cleanup : vim-minimal-2:7.3.1314-1.fc19.x86_64 927/927 /sbin/dracut: line 871: /etc/crypttab: No such file or directory Verifying : xorg-x11-xbitmaps-1.1.1-5.fc19.noarch 1/927 ... Version-Release number of selected component (if applicable): dracut-029-2.fc19.x86_64 Not having /etc/crypttab should be silently ignored imho.
commit 1ae8b8aa0281102dd66f14fca8f2342a2608fb10 commit 7deba0428a23b3f410a7cf8cac7cf8355e4dc150
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.