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.
Loading…
ReadMeFeed / Community knowledge
#appstream
Real questions. Useful conversations. Find the people who know your stack.
Managing Application Lifecycles in Rocky Linux with AppStream
Learn how to use Rocky Linux AppStream to manage multiple software versions without compromising OS stability, including a practical guide to DNF module streams.
rockylinuxAlmaLinux AppStream: Modular Package Management for Enterprise Servers
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.
Managing Application Lifecycles with AlmaLinux AppStream Modules
Learn how to use AlmaLinux AppStream modules to manage multiple software versions (streams) on a single OS deployment without breaking system dependencies.
AlmaLinux 9 AppStream Module Stream EOL Transitions Disrupt Container Build Reproducibility
Context AlmaLinux 9 manages languages, databases, and tools through modular streams in the AppStream repository, each with a published end-of-life date. When a stream expires, dnf automatically switches to the default stream for that module, which can also change between minor releases such as 9.2 and 9.3. Problem In a pinned development environment—containe
Failed to resolve module stream in dnf module
CentOS 8 delivers multiple application versions through dnf module streams provided by AppStream repositories. The dnf module command relies on module stream metadata to enable, disable, or install streams. When the resolver cannot locate requested metadata, dnf emits 'Failed to resolve module stream'. The current message offers limited feedback about whethe
centosAlmaLinux AppStream: enabled module stream past EOL with no warning from dnf
Goal I want a reliable way to detect, before patching or provisioning, whether any enabled AppStream module stream on an AlmaLinux 9 system has passed its end-of-life date, so I can plan a stream switch before security updates stop. Constraints and uncertainty From what I understand, only one stream per module can be enabled at a time, and an EOL stream rema
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. Curren
AppStream module stream transitions between Rocky Linux 8 and 9
DNF Module Stream Consistency Rocky Linux 8 and 9 utilize AppStream modules to provide multiple versions of the same software package. While these distributions target binary compatibility with RHEL, the default module streams may vary between minor releases or differ when transitioning from version 8 to 9. When automating deployments across these versions,