| 1 |
> On 25 Nov 2021, at 13:59, Thomas Deutschmann <whissi@g.o> wrote: |
| 2 |
> If you do a normal world upgrade, this is the default portage behavior, not? I.e. package manager will downgrade if you don't stop. And especially on servers, people tend to use cronjobs/scripts to do that... |
| 3 |
|
| 4 |
I would really not recommend doing this and I say this regularly. We expect users to: |
| 5 |
- read elog output; |
| 6 |
- read news items first; |
| 7 |
- read pkg_pretend / pkg_postinst output which may be critical and needed to be acted on soon (even if it's accompanied by a news item, although it isn't always). |
| 8 |
|
| 9 |
Should we try to improve that situation? Yeah, I think so, but that's really not the case right now. |
| 10 |
|
| 11 |
> And forcefully here refers to the undesirable result (at least that was my intention). Something the user doesn't want. |
| 12 |
|
| 13 |
As we've discussed at length during the "Bitcoin consent" issue (wrt Taproot), users are expected to read and verify world upgrade output before proceeding. |
| 14 |
|
| 15 |
We have similar issues with e.g. new major glibc versions (you shouldn't do this unless you're in a position to restart at least several services). |
Archives