| 1 |
On Thu, Nov 25, 2021 at 8:59 AM Thomas Deutschmann <whissi@g.o> wrote: |
| 2 |
> |
| 3 |
> Hi, |
| 4 |
> |
| 5 |
> On 2021-11-25 04:49, Mike Gilbert wrote: |
| 6 |
> > On 2021-11-21, keywords for dev-db/mariadb-10.6 were removed to |
| 7 |
> > address a file collision with dev-db/mariadb-connector-c. This |
| 8 |
> > unintentionally triggered a version downgrade for users who had |
| 9 |
> > successfully upgraded to dev-db/mariadb-10.6 already. |
| 10 |
> |
| 11 |
> Works for me. However, I would write dev-db/mariadb:10.6. Is that |
| 12 |
> acceptable for you? |
| 13 |
|
| 14 |
Sure. |
| 15 |
|
| 16 |
> > I don't like the phrase "forcefully downgraded" here. This implies |
| 17 |
> > that something happened without the user's consent. emerge would have |
| 18 |
> > informed them of the downgrade before it happened. I would suggest |
| 19 |
> > removing the word "forcefully" from these paragraphs. |
| 20 |
> |
| 21 |
> If you do a normal world upgrade, this is the default portage behavior, |
| 22 |
> not? I.e. package manager will downgrade if you don't stop. And |
| 23 |
> especially on servers, people tend to use cronjobs/scripts to do that... |
| 24 |
|
| 25 |
Something happening by default is not the same as forcing it to happen. |
| 26 |
|
| 27 |
Using a cron job or other blind automation to do package upgrades on |
| 28 |
any production system is a bad idea. We certainly do not recommend |
| 29 |
that to people, nor force them to do it. |
| 30 |
|
| 31 |
> And forcefully here refers to the undesirable result (at least that was |
| 32 |
> my intention). Something the user doesn't want. |
| 33 |
|
| 34 |
That's really not what "forcefully" means. It would be fine to use |
| 35 |
"unintentional" or "unwanted" in its place. |
Archives