Citeren Oleksii Vilchanskyi <oleksii.vilchanskyi@gmail.com>:
Obviously, nobody can remember to manually run a program to check for .rpmnew every upgrade. Can zypper notify about this at the end automatically? The only reference I found googling "zypper notify about rpmnew" was [0] with a broken link to openFATE. Was it ever implemented?
[0]: <https://lists.opensuse.org/opensuse-features/2013-02/msg00022.html>
I also would have been useful to indicate the changes between the previous configuration file and the new one. Chances are there were local modifications that prevented mariadb from starting. In my case, all was well after running 'zypper dup'.
On 24/08/2019 09:44, Philippe Conde wrote:
Hello,
After zypper dup mariadb cannot be started. Replacing old "/etc/cnf" by "/etc/my.cnf.rpmnew" solves the problem. Regards
Dominique Leuenberger a écrit :
Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here.
Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&version=Tumbleweed&build=20190822
Please do not reply to this email to report issues, rather file a bug on bugzilla.opensuse.org. For more information on filing bugs please see https://en.opensuse.org/openSUSE:Submitting_bug_reports
Packages changed: PackageKit fwnn libetonyek (0.1.8 -> 0.1.9) libreoffice librevenge libsrtp2 (2.1.0 -> 2.2.0) mariadb (10.2.24 -> 10.3.17) rubygem-sassc (2.0.1 -> 2.1.0) shotwell (0.30.5 -> 0.30.7) yum
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org