You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 13, 2021. It is now read-only.
When some module requests specific rpm for correct functionality (to be able to provide full possible check), current message printed by PA is confusing. See mysql/configuration_changes, that is applied when the mysql-libs rpm is installed, but require the mysql rpm for correct checking of configuration.
In case the mysql rpm is not installed, you can see this message:
preupg.risk.HIGH: Package mysql is not installed.
preupg.risk.HIGH: Please, install all required packages (and binaries) and run preupg again to process check properly.
The message should provide better clarification for user, why the package should be installed. Like:
preupg.risk.HIGH: The mysql-libs cannot be checked properly because these required packages are missing: pkg1, pkg2, pkg3, ....
preupg.risk.HIGH: Please, install all required packages for correct run of the module.
That's just draft text. You can choose whatever text you want, that will be clear for user.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When some module requests specific rpm for correct functionality (to be able to provide full possible check), current message printed by PA is confusing. See
mysql/configuration_changes
, that is applied when themysql-libs
rpm is installed, but require themysql
rpm for correct checking of configuration.In case the
mysql
rpm is not installed, you can see this message:The message should provide better clarification for user, why the package should be installed. Like:
That's just draft text. You can choose whatever text you want, that will be clear for user.
The text was updated successfully, but these errors were encountered: