ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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
Stale DNF metadata after system clock rollback The goal is to understand how DNF decides whether its cached repository metadata remains valid when the system clock is set backward, potentially bypassing the metadata_expire timer. Constraints include differences in cache layout and expiration logic between DNF releases prior to version 4.0 and later versions,
Goal: Determine whether turning on DNF's asynchronous, parallel metadata downloads by default reduces overall transaction time on typical Fedora Workstation hardware without exacerbating I/O contention during large package upgrades. Uncertainty: While parallel downloads can cut wall‑clock latency, they may increase simultaneous read/write requests, raising q
Fedora utilizes Btrfs snapshots to facilitate system state recovery, allowing users to boot into previous root filesystem states via the GRUB menu. This mechanism provides a method for reverting OS-level changes and configuration errors. A potential conflict arises when the DNF package manager modifies the RPM database. Because the RPM database is stored wit
Cache Expiration Behavior DNF caches repository metadata under /var/cache/dnf with a configurable metadata_expire value that defaults to six hours for new metadata and thirty days for previously successful metadata. The setting controls when an automatic refresh is triggered, yet the exact interaction between the expire window, explicit dnf makecache calls,
Rocky Linux uses DNF to manage packages, and its download layer retries transient network failures according to configured retry, timeout, and minrate values. Completed payloads are written to temporary files and renamed into place, which prevents duplicated or truncated package files on a re-attempted download. The unresolved boundary sits at the RPM transa
Fedora's DNF package manager downloads package payloads and repository metadata, but the default policy for incomplete files after a user cancellation or network timeout is not codified in the documentation. Administrators who manage automated mirrors or limited-bandwidth environments need a reliable way to predict whether partial downloads are discarded aut
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
fedora
rockylinux
centos