[MIR] mysql-8.4
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mysql-8.4 (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
This MIR will allow packages in main to migrate from depending on mysql-8.0 with libmysqlclient21 to mysql-8.4 with libmysqlclient24. Since mysql-8.0 did not have an MIR bug for the transition from mysql-5.7, I created this as a new one.
[Availability]
The package mysql-8.4 is already in Ubuntu universe (in plucky-proposed).
The package mysql-8.4 builds for the architectures it is designed to work on.
It currently builds and works for architectures: amd64, arm64, ppc64el, riscv64, and s390x for server and client; and armhf and i386 for client-only. The package still needs to be allowed to build for i386 in the archive though.
Link to package https:/
[Rationale]
- The package mysql-8.4 is required in Ubuntu main for migrating our MySQL version from 8.0 to 8.4
- The package mysql-8.4 will generally be useful for a large part of our user base
- This will allow packages to build against the LTS libmysqlclient24 library
- There is no other/better way to solve this that is already in main or should go universe->main instead of this.
- The package mysql-8.4 is required in Ubuntu main no later than the release of plucky to make it our main supported MySQL version
[Security]
- Had various security issues in the past: https:/
CVEs are fixed internally upstream with each new minor release.
- Binary mysqld in sbin is no problem because it already exists there in mysql-8.0
- Package does install services, timers or recurring jobs - mysql.service
- Security has been kept in mind and common isolation/
apparmor profile in debian/
- Packages does not open privileged ports (ports < 1024).
- Package does expose an external endpoint, it is localhost:3306 which allows access to the mysql server from a client.
- Packages does not contain extensions to security-sensitive software (filters, scanners, plugins, UI skins, ...)
[Quality assurance - function/usage]
- The package works well right after install
[Quality assurance - maintenance]
- The package is maintained well in Ubuntu and Upstream and does not have too many, long-term & critical, open bugs
- Ubuntu https:/
- Upstream's bug tracker - https:/
- The package does not deal with exotic hardware we cannot support
[Quality assurance - testing]
- The package runs a test suite on build time, if it fails it makes the build fail for amd64 and arm64, link to build log https:/
- The package runs an autopkgtest, and is currently passing on all architectures - https:/
- The package does have not failing autopkgtests right now
[Quality assurance - packaging]
- debian/watch is present and works
- debian/control defines a correct Maintainer field
- This package does not rely on obsolete or about to be demoted packages.
- This package has no python2 or GTK2 dependencies
- The package will not be installed by default
- Packaging is complex, but that is ok because MySQL is a complex package. The rules file has been cleaned up from the 8.0 version
[UI standards]
- Application is end-user facing via CLI, Translation is present, via standard intltool/gettext or similar build and runtime internationaliz
[Dependencies]
- No further depends or recommends dependencies that are not yet in main
[Standards compliance]
- This package correctly follows FHS and Debian Policy
[Maintenance/Owner]
- The owning team will be Ubuntu server and I have their acknowledgement for that commitment.
- The future owning team is not yet subscribed, but will subscribe to the package before promotion
- This does not use static builds
- This package uses vendored code (boost1.84), which is refreshed by upstream during security updates
- This package is not rust based
- The package has been built within the last 3 months in the archive
- Build link on launchpad: https:/
[Background information]
Upstream Name is mysql-8.4
Link to upstream project https:/
Additional info:
Security maintenance for mysql-8.4 will match that of mysql-8.0, in that each new minor version will be backported to existing releases. MySQL's upstream release model does not describe CVE fixes individually, so all fixes are backported each time.
Additionally, with the removal of 32-bit support upstream, our support for mysql on 32-bit platforms has been reduced to mysql-client and the client libraries only.
