| 1 |
On Thu, 2021-11-25 at 17:21 +0100, Piotr Karbowski wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> On 25/11/2021 16.50, Pacho Ramos wrote: |
| 5 |
> > As a side note, maybe ebuild should add sanity checks (like those from |
| 6 |
> > glibc) to |
| 7 |
> > prevent downgrades, otherwise people could still accidentally hit the |
| 8 |
> > issue |
| 9 |
> |
| 10 |
> You might have valid use cases to downgrade mysql, if you are okay not |
| 11 |
> preserving data. I'd assume it's a common knowledge that downgrade of |
| 12 |
> any data store, be that database or likes like elasticsearch, will |
| 13 |
> corrupt the data. |
| 14 |
> |
| 15 |
> To make it actually useful I think we'd need new EAPI feature |
| 16 |
> 'downgrade-protection', that unless is explicit ignored like |
| 17 |
> --ignore-downgrade-protection mysql, it would prevent it from happening. |
| 18 |
> |
| 19 |
> -- Piotr. |
| 20 |
> |
| 21 |
|
| 22 |
https://github.com/gentoo/gentoo/blob/master/sys-libs/glibc/glibc-2.34-r2.ebuild#L643 |
Archives