DNF Migration testing overview

[Brian C. Lane]

On Fri, Feb 20, 2015 at 05:38:03PM -0700, Mike Ruckman wrote:
> Greetings Testers!
> 
> With the F22 switch from yum to dnf as a package manager, there was a need to
> figure out what the scope would be for QA testing. Naturally, to define the
> scope for a subset, I had to figure out (at least in a general sense) how
> large the complete set is. There's a multitude of complication vectors with a
> switch like this - especially since dnf is specifically designed to not be a
> drop in replacement for yum.
> 
> First question: Who/what all uses yum?
> --------------------------------------
> 
> Swapping out yum is the equivalent of someone coming up with a new form of
> hemoglobin, then trying to figure out what all could go wrong when you make
> the swap (tl;dr: Everything). The first to come to mind is anyone who installs
> packages from the CLI. But then you have all the GUI front-ends (PackageKit
> and Apper) and all the build tools - not to mention the installer.
> 
> Some places yum touches:
>  - Oz/ImageFactory (Building Cloud images)
>  - koji (RPM-based build system)
>  - pungi (Build installation trees and isos)
>  - ABRT (Automatic Bug Reporting Tool)
>  - Anaconda (Fedora installer)
>  - liveimage-creator (tool for creating live images)
>  - cloud-init (tool for configuring freshly launched cloud images)
>  - FedUp (tool for updating Fedora between releases)
>  - Software Center and Apper (Default software installers)
>  - rolekit (tool to easily deploy roles to a Server installation)
>  - virt-builder and friends (tools for manipulating virtualized environments)

There is also lorax (used to create boot.iso). For F22 lorax will
continue to use yum.  But there is a f22-dnf-branch you can test with if
you want.

https://github.com/rhinstaller/lorax/tree/f22-dnf-branch

For F23 lorax is already using DNF with lorax-23.1

-- 
Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT)