Details
-
Task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
This is a container for all issues related to upgrading packages
Attachments
Issue Links
- includes
-
MDEV-3950 mariadb rpms should not obsolete mysql?
- Closed
-
MDEV-4151 Error message on an attempt of RPM upgrade from one major version to another mixes up MySQL and MariaDB
- Open
-
MDEV-4268 Galera server cannot be installed via yum over MariaDB server and vice versa
- Closed
-
MDEV-9584 Upgrading MariaDB 5.5 to 10.1.11 fails with RPM
- Stalled
-
MDEV-9660 yum/rpm update from 10.0 to 10.1 replaces/obsoletes ?
- Closed
-
MDEV-9766 Testing for MDEV-9584 (Relaxed rules for yum upgrade)
- Stalled
-
MDEV-9796 MariaDB cannot be installed from MariaDB's repo on openSUSE 13, SLES12: conflict with the default repo
- Closed
-
MDEV-9797 After upgrade from Galera server does not get restarted automatically on CentOS, RHEL, Fedora, SUSE
- Open
-
MDEV-9805 After upgrade from distro's mariadb on CentOS 7 fails to restart
- Open
-
MDEV-9807 MariaDB-server does not replace MariaDB-Galera-server upon upgrade on Fedora, SUSE
- Open
-
MDEV-9808 MariaDB-server does not replace mariadb-server from distro on Fedora
- Open
-
MDEV-9809 Transaction check error upon installing MariaDB-server and MariaDB-client over previously installed mariadb-server + mariadb from distro on Fedora
- Open
-
MDEV-9810 Upgrade which fails suggesting FORCE_UPGRADE is not transactional, it installs some packages but not all
- Open
-
MDEV-9813 MariaDB-shared cannot be installed over mysql-community-common on RHEL5
- Closed
-
MDEV-9815 MariaDB components do not replace mysql51-mysql* or mysql55-mysql* on RHEL5 and CentOS5, instead get installed side by side
- Closed
- is part of
-
MDEV-22323 Upgrading MariaDB
- Open