Description of problem: It seems Anaconda is not expected to work without tmux. Therefore I think it makes sense to add a 'Require: tmux' to the spec file. Version-Release number of selected component (if applicable): 27.11-1 How reproducible: always Steps to Reproduce: 1. remove tmux from lorax template 2. generate boot.img and try to do an installation 3. the installation will fail mid-way through Actual results: Anaconda fails without tmux but tmux is not a runtime requirement. Expected results: Anaconda requires tmux. Additional info:
Anaconda can be also installed as an application & used to install into a local folder or into an image. This can be for example used to generate containers. In such case Tmux is not needed, so having it as a "hard" runtime dependency seems superfluous. Having tmux in the template IMHO makes sense (as it actually needed in the installation environment, unlike when Anaconda is installed as an application).
The thing is this breaks installations with custom templates that don't explicitly install tmux as it doesn't appear to be necessary until it's quite late. It's just yet another thing one needs to keep in mind & alter their templates as anaconda's requirements evolve over time. If parts of anaconda depend on it, it should be a runtime dependency of a package that provides those. Perhaps this could be a subpackage that wouldn't need to be installed in scenarios you are describing.
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.