Details
-
Task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
Description
When doing a debian/ubuntu upgrade, if you have mariadb installed and stopped as a service, the process of doing an `apt-get upgrade` shouldn't start the mariadb service.
This applies both to systemd and sysv.
Additionally for systemd, systemd multiinstances e.g.`mariadb@xyz`, those that are started before the upgrade, should be stopped, and restarted after the upgrade.
Attachments
Issue Links
- relates to
-
MDEV-17739 mariadb-server-10.1: Updates not restarting mariadb@xx services
-
- Open
-
-
MDEV-23050 MariaDB Server failure on Proxmox (with Ubuntu 20.04 and Systemd)
-
- Closed
-
-
MDEV-23755 safety for upgrades (innodb) and packaging
-
- Closed
-
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue relates to |
Remote Link | This issue links to "Maintainer Scripts graphs on script ordering (Web Link)" [ 30200 ] |
Remote Link | This issue links to "debian-policy: maintainer scripts (Web Link)" [ 30201 ] |
Link |
This issue relates to |
Assignee | Otto Kekäläinen [ otto ] |
Assignee | Daniel Black [ danblack ] |
Remote Link | This issue links to "debian systemd maintainers non-answer (Web Link)" [ 32332 ] |
Remote Link | This issue links to "SO - mysql equivilant problem (Web Link)" [ 32333 ] |
Remote Link | This issue links to "dh_installsystemd source code (Web Link)" [ 32334 ] |
Workflow | MariaDB v3 [ 111770 ] | MariaDB v4 [ 131344 ] |
Assignee | Daniel Black [ danblack ] |
Link | This issue relates to MDEV-17739 [ MDEV-17739 ] |
Fix Version/s | 10.1 [ 16100 ] |