On Tue, Oct 4, 2016 at 10:51 AM, Andrew Lutomirski <luto(a)mit.edu> wrote:
By that standard, why do we support dnf at all?
$ sudo dnf upgrade
Error: dnf upgrade is dangerous. Use PackageKit instead and reboot when asked.
Well it's not always risky, it depends on what's being updated. If
it's applications, it's pretty safe unless they're running. There is a
qualitative difference between server and workstation, so the warning
may be misleading if it exists on server also.
I, for one, *like* not rebooting, and I'm perfectly capable of
rebooting manually if stuff breaks. As far as I know, Fedora
considers plain ol' dnf to be supported.
Yeah this is really debatable for best practices to expect users to
know these things. You can argue if they're using dnf they should know
better, and just accept that things can blow up, or help track them
down so if possible this stuff can get fixed.
For server use, I'm not convinced that the offline update
supported (at the very least, I have no idea how to trigger it), and
servers have the same issue.
PackageKit is installed on server, so while I haven't tested it, it
seems plausible it could be used for system updates. But I think the
risk here is much less because dnf is a bit more isolated by not
running in a GUI Terminal in a user session. But even here, a reboot
is expected for many things, there's just no guarantee of state
I think the thing that's unique with current offline updates compared
to other platforms I use is the double reboot. The reboot to get to
offline updates target where the update happens, and then a reboot to
get back to graphical target. That does seem suboptimal to me, where
other platforms just log out the user session, and drop to their
reduced function "updates" state to do the update, and then there's
Anyway, my opinion is that Workstation folks should use Gnome Software
to do their updates, and if there's something wonky there, we need to
get it fixed. That's the default and primary update method. Within
something like 5 minutes of first boot after an installation,
PackageKit is already downloading updated packages. Unless that's
disabled, a 'dnf update' is going to unnecessarily download those
packages in duplicate.