On Thu, 2016-10-06 at 00:05 +0200, Kevin Kofler wrote: > Adam Williamson wrote: > > I don't want to get in the KDE folks' bad graces, but this likely could > > also affect KDE's graphical update system, so I'd advise against using > > that for the present too. > > > Offline updates in KDE are just not going to happen any time soon. > > > I also don't see offline updates as a reasonable solution to this problem: > > * For this particular crash, the bug should simply be tracked down and > fixed. We already did that, but two things: 1) that doesn't do a damn thing to help anyone who ran into it before we tracked it down and fixed it. Offline updates sure were a great *mitigation* before we fixed the bug. 2) the short-term fix is to remove the service restart from the package scriptlets, but because the service restart was in the %postun scriptlet, the update can't fix it immediately: indeed, *installing* the update will inevitably trigger the bug. The update can only prevent it happening for *subsequent* updates. > * As a general workaround for this type of crashes, we need a > complete-transaction command in DNF – please add your voices to: > https://bugzilla.redhat.com/show_bug.cgi?id=1091702 > – and not the sledgehammer approach of doing all updates offline. I'm certainly not opposed to improving the experience of recovering from this kind of crash, but I'm really not a big fan of the message 'if the update process happens to crash X, hope you understood what happened, and here's the magic recovery command you can run'. I honestly think GNOME has this exactly right for the 'general' user: the safe thing to do is to strongly encourage offline updates, i.e. don't offer any online update mechanism through the desktop. In a completely practical sense, given the current state of the tools and the fact that we know bugs like this crop up - not *often*, but more than *never* - I think it's a more responsible approach than running the update process inside the desktop session. Could KDE perhaps look into making it so the update process runs outside of the desktop session somehow, if it's not going to go to full-on offline updates 'any time soon'? I know this decision has its own complexities, though. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
