Managing Software Versioning in AlmaLinux using AppStream Modules
Learn how to use AlmaLinux AppStream to manage multiple software versions of the same package without upgrading your entire OS, using the dnf module system.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to use AlmaLinux AppStream to manage multiple software versions of the same package without upgrading your entire OS, using the dnf module system.
Learn how to use Rocky Linux AppStream to manage multiple software versions without compromising OS stability, including a practical guide to DNF module streams.
AlmaLinux’s AppStream lets you run multiple application streams side‑by‑side. This blog explains how to enable, use, and switch streams—like Node.js 18 and 16—while highlighting trade‑offs for enterprise servers.
Enable Rocky Linux PowerTools to access development packages like gcc and make. Follow a simple three‑step process: enable the repo, refresh metadata, install and verify. Understand security limits and common pitfalls before turning on PowerTools.
Learn how to use AlmaLinux AppStream modules to manage multiple software versions (streams) on a single OS deployment without breaking system dependencies.
Learn how to enable, use, and reset DNF module streams on Rocky Linux to get exact versions like Node.js 14, with steps, trade‑offs, and a reset procedure.
After adding a new software repository on a Fedora system, DNF may continue to use outdated metadata from its local cache, causing dependency resolution errors or missed package updates. I need a way to assess whether the cached metadata for that repository is still fresh without clearing the entire cache or affecting other repositories. The assessment shoul
Goal Determine whether a module stream enabled on Rocky Linux 8 remains active after upgrading to Rocky Linux 9. Constraints and Uncertainty The dnf module system records enabled streams and preserves them across minor releases, but the official documentation does not specify how stream state is handled during a major distribution upgrade. Reproducible build
Background CentOS 8 replaces the legacy yum binary with dnf , retaining a yum symlink for backward compatibility. The symlink masks underlying differences in dependency resolution, exit codes, and option handling (e.g., --setopt ). Scripts that rely on exact yum output or exit status may fail silently when dnf is invoked through the alias. Unresolved Decisio