Merge lp:~paride/britney/mysql-8 into lp:~ubuntu-release/britney/hints-ubuntu
Proposed by
Paride Legovini
Status: | Rejected |
---|---|
Rejected by: | Steve Langasek |
Proposed branch: | lp:~paride/britney/mysql-8 |
Merge into: | lp:~ubuntu-release/britney/hints-ubuntu |
Diff against target: |
12 lines (+2/-0) 1 file modified
ubuntu-release (+2/-0) |
To merge this branch: | bzr merge lp:~paride/britney/mysql-8 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Steve Langasek | Disapprove | ||
Review via email: mp+384720@code.launchpad.net |
Commit message
force-reset-test libdbd-
To post a comment you must log in.
Unmerged revisions
- 4860. By Paride Legovini
-
force-reset-test libdbd-
mariadb- perl/1. 11-3ubuntu2
My second take at this :)
This change will allow mysql-8. 0/8.0.20- 0ubuntu1 to migrate from groovy-proposed. According to
LP: #1877504 there is an actual regression in MySQL 8.0.20 and a proper patch is being worked on, however we are in a situation where:
* MySQL 8.0.20 already made it into Focal via the security pocket as version mysql-8. 0/8.0.20- 0ubuntu0. 20.04.1, uploaded to fix the CVEs mentioned in the changelog, therefore: mariadb- perl.
* The regression already hit Focal, where we mostly want to avoid regressions, and:
* Groovy has unfixed CVEs, as the regression was caught by a failing autopkgtest on libdbd-
* A proper fix is being worked on, but we can't know how much time will be needed to get it right and validate it.
* The regression is hit only when using mariadb, which is from universe, while mysql-8.0 is in main.
In my opinion migrating mysql-8. 0/8.0.20- 0ubuntu1 and having the CVEs fixed is more important than avoiding a regression that already hit Focal.