Created attachment 1448652 [details] mentioned error is on line 3106 Description of problem: Kickstart F28/x86_64 system installation, where %packages section of kickstart file contain "dovecot", results in an error window being displayed with message as "ERR dnf.rpm: Non-fatal POSTIN scriptlet failure in rpm package dovecot" with only "Quit" button within it (no other buttons as Ignore/Continue etc). Version-Release number of selected component (if applicable): anaconda 28.22.10-1.fc28 dovecot-1:2.2.35-2.fc28.x86_64 Expected results: IMHO anaconda should ignore similar non-fatal error (maybe log them for later analysis) or should in its error window offer some Continue button. Additional info: Installation itself continues, as it's obvious from logs. I did not have the strong enough nerves to get it to the end.
All RPM errors are fatal (see https://bugzilla.redhat.com/show_bug.cgi?id=1565123). Reassigning to dovecot.
Imho better should be prefer to have (in case of non-fatal error) installed system than abort installation: - when these errors will be logged, is possible to report all problematic packages together (instead of discarding individual packages or entire package groups) - There are too many packages and these are changed throughout the distribution life - thus such situations will occur quite often. This means a lot of lost time on the installers side - who use kickstart to make the installation reproducible, accurate and _fast_. This solution is contraproductive. - perhaps I'm not one, which prefer to have installed Fedora system (no matter whether with or without one - two maybe badly (but in this cases is perhaps all OK) installed packages (which will be easy tested and repaired afterwards), than aborted installation. And, personally, I would like to see if the installation media (like Fedora-netinst-ARCH.iso) is updated over the life of the distribution, as anaconda bugs are continually fixed. I'm sure there are lot of test before new distro release, but in case high degree of complexity as installer has some bugs will always remain - and this could help to remove them more quickly.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.