1 |
On Wed, Nov 24, 2021 at 10:21 PM Thomas Deutschmann <whissi@g.o> wrote: |
2 |
> +On 2021-11-21, a member of the QA project accidentially de-keyworded |
3 |
> +MariaDB 10.6 to address a file collision, users, who also had latest |
4 |
> +dev-db/mariadb-connector-c installed, experienced (NOTE: The default |
5 |
> +MySQL connector in Gentoo Linux is provided by |
6 |
> +dev-db/mysql-connector-c) [Link 1]. |
7 |
|
8 |
This sentence is very difficult to read. Also, I don't think it is |
9 |
relevant to call out the mistake by the QA team in a news item |
10 |
intended for end users. I would rewrite this as: |
11 |
|
12 |
On 2021-11-21, keywords for dev-db/mariadb-10.6 were removed to |
13 |
address a file collision with dev-db/mariadb-connector-c. This |
14 |
unintentionally triggered a version downgrade for users who had |
15 |
successfully upgraded to dev-db/mariadb-10.6 already. |
16 |
|
17 |
> +However, downgrades are not supported in MySQL/MariaDB [Link 2]. |
18 |
> + |
19 |
> +In case you already fully upgraded to MariaDB 10.6 (which includes |
20 |
> +executing mysql_upgrade command) and forcefully downgraded your |
21 |
> +MariaDB instance afterwards during the time window when keywords were |
22 |
> +removed, you maybe experiencing different problems: |
23 |
> + |
24 |
> +At best, your forcefully downgraded MariaDB instance prevented startup |
25 |
> +so all you have to do is upgrade to MariaDB 10.6 again to resume |
26 |
> +services. |
27 |
|
28 |
I don't like the phrase "forcefully downgraded" here. This implies |
29 |
that something happened without the user's consent. emerge would have |
30 |
informed them of the downgrade before it happened. I would suggest |
31 |
removing the word "forcefully" from these paragraphs. |