#18374 closed enhancement (fixed)
mariadb-10.11.4
| Reported by: | Douglas R. Reno | Owned by: | Douglas R. Reno |
|---|---|---|---|
| Priority: | elevated | Milestone: | 12.0 |
| Component: | BOOK | Version: | git |
| Severity: | normal | Keywords: | |
| Cc: |
Description ¶
New minor version
We will have to run 'mariadb-upgrade', but we've already got instructions for that in the book.
This will fix CVE-2022-47015 too.
Change History (6)
comment:1 by , 20 months ago
comment:2 by , 20 months ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 20 months ago
Here's some of the details on MariaDB-10.11.x: https://mariadb.com/kb/en/changes-improvements-in-mariadb-1011/
For upgrading an existing system: https://mariadb.com/kb/en/upgrading-from-mariadb-10-6-to-mariadb-10-11/ - no configuration changes seem to be needed, at least to the configuration in the book.
comment:4 by , 20 months ago
Fixed at bca6a1270279325c2ded5ee15dba9aac5834da44
Security advisory to come later.
comment:5 by , 20 months ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
This also covers a build failure that happens due to GCC-13 changes.