On Tue, Oct 4, 2016 at 11:39 AM, Gerald B. Cox <gbcox(a)bzb.us> wrote:
On Tue, Oct 4, 2016 at 10:05 AM, Kevin Fenzi <kevin(a)scrye.com> wrote:
> Well, the problem there, what do you mean by 'support'?
> In this case lots of people use dnf for updates, so IMHO it would be
> "we will try and keep this working, and fix anything we can, but do
> understand that there's a low level problem here that something could
> mess up updates in progress, if you want to be more sure of not hitting
> problems, use the offline updates in your graphical desktop"
OK, I'm completely confused.
First of all, I've never seen a message such as:
> Error: dnf upgrade is dangerous. Use PackageKit instead and reboot
> when asked.
That was a suggested change to inform the user.
It's an OK idea. With "atomic" deployments (those that are rpm-ostree
based) the 'dnf update' command hard fails. You're expected to use
'rpm-ostree upgrade' which itself would be integrated into the
and I have NEVER used the graphical update since the first release of
Fedora. I've always used yum or dnf. As I mentioned earlier in the past
I've found the graphical tools to be quirky at best - perhaps that has
changed, but since the command line has always worked for me, I've stuck
with it. Apparently I've missed something along the way because now people
are implying that using the command line tools from within GNOME or KDE are
dangerous. What exactly is going on?
This is old news. It's come up on this list numerous times. It's the
*entire* reason why offline updates exists. Not doing them offline is
know to entail all kinds of non-deterministic risks.
As far as rebooting after every update? Huh? Who does that?
Strictly speaking it's not necessary for every update, there's just no
mechanism for knowing for sure what updates entail more risk than
others. You'll notice that once an application is installed, whether
by dnf or Gnome Software, it's considered part of the system. There's
no separation of OS upgrades from application updates. The former
entail a lot more risk than the latter. In the near future, I expect
flatpak applications can be updated in place, once complete you'd get
a prompt to relaunch the application to use the update one, or
something like that.
Yes, we're Windows. Is that what you want to hear? I don't understand
why you think this is a question to be taken seriously rather than
And by the way, macOS does the same thing. The main difference there
is application updates rarely require reboots, because applications
are self contained. You do have to quit them for the update to get