minimizing dnf transaction size

asked 2015-11-12 12:16:49 -0500

this post is marked as community wiki

This post is a wiki. Anyone with karma >750 is welcome to improve it.

I had 2 cases where one package out of a large transaction[1] could not be rolled back, preventing the rollback of many packages.

So for future safety are there ways of minimizing dnf transaction size- keeping the number of packages upgraded in one transaction at the smallest possible?

[1] one where many packages were upgraded

edit retag flag offensive close merge delete



Update your system more often ? When a large number of packages become available, only install a few manually rather then all of them ? Manually downgrade ?

bodhi.zazen gravatar imagebodhi.zazen ( 2015-11-12 13:27:42 -0500 )edit

this is exactly what I was doing & will not do again, after losing 2 hours on debugging a problem I created for myself doing this.

Here's the dumb mistake: upgraded nss but not other related stuff - the problem I created for myself

sksharma gravatar imagesksharma ( 2015-11-19 12:08:26 -0500 )edit