On Tue, Mar 30, 2021 at 06:54:25PM +0000, Gary Buhrmaster wrote: > On Tue, Mar 30, 2021 at 6:18 PM Zbigniew Jędrzejewski-Szmek > <zbyszek@xxxxxxxxx> wrote: > > > There is no good way to do this. > > This is one of those cases where I occasionally > miss a mainframe fix update feature to prevent > certain bad automated results. > > In SMP/E, there was the concept of HOLD's for > a fix. There were a number of HOLD reasons, > but one was ACTION, which prevented the > application of the fix unless the HOLD was > released. I.e. you had to read the docs and > either do, or prepare to do, whatever the > ACTION said to do before you could proceed FWIW, with Debian's apt, that's more or less what you get: the upgrade will block and ask questions. We have never done this in the rpm world, and while sometimes this makes things harder, I think this is the right choice in the long run. Essentially, interactive questions during upgrades are are fine as long as you have one or two or three servers per human, *and* the human has time and knowledge and energy to deal with the questions. But the world has changed, and we have many more machines per person, and many more non-power users then ever. Zbyszek _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
