Hacker News new | past | comments | ask | show | jobs | submit login

This isn't really DNF specific — it can happen with any package manager. Whenever I run a DNF update that is going to affect X or my GNOME session, I run it in tmux. There's not really a good solution _other_ than that, which is why the desktop team promotes the reboot-to-apply-updates approach for the general case. It's annoying to have to do that, but it's very reliable. (Or, if you're more tech savvy, the tmux or switch-to-a-VT thing is just fine.)



> This isn't really DNF specific — it can happen with any package manager

I don't know about other package managers, but please don't generalize dnf's behavior here to the others, because apt-get and dpkg would be just fine in this case. You can even disconnect from the ssh session and apt-get will continue until it is finished. In the worst case scenario you would call apt-get -f install and it would continue where it's left.

> There's not really a good solution _other_ than that,

Of course offline updates are valuable for the 0.001% scenarios but there are basic resiliency measures one should take while writing the basic building block of the distribution, before throwing in the towel and suggesting running it inside tmux or to use offline updates for everything.


> I don't know about other package managers, but please don't generalize dnf's behavior here to the others, because apt-get and dpkg would be just fine in this case.

This claim is not matched by my personal experience. Recovery is usually possible, but depending on the particulars may require non-trivial efforts.


apt-get -f install is hardly non-trivial.


My point is that "apt-get -f" works less than 100% of the time, contrary to the "would be just fine" claim.


> works less than 100% of the time

I can't say much about that without seeing some examples. Of course it may not calculate&offer an ideal strategy or even outright choke if the system is put into a manually induced dependency hell, but that's a different scenario than resuming an interrupted process which was otherwise progressing OK.


I'm sure there are some things that could be done better. In particular, DNF could do with better completion of interrupted transactions — the session dying is only one possible interruption.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: