DNF Modularity: Transitioning software streams in AlmaLinux 9

Stream Management in AppStream

AlmaLinux 9 uses the DNF package manager with the AppStream model, allowing multiple versions of a software stream (e.g., Node.js, Python) to coexist.

When a system has a module stream already enabled, switching to another stream often triggers dependency conflicts because the previous stream’s packages remain installed.

Current documentation states that a dnf module reset is usually required before activating a new stream, but it is unclear whether this command fully cleans all related dependencies or if manual intervention is necessary.

• What is the precise sequence to switch streams without leaving orphaned packages?
• Does dnf module reset remove all packages that belong to the previous stream, or are some retained?