Description of problem: Ramalama was configured in Packit to build only for epel10 and epel10.0. This has resulting in epel10.1 falling behind both of those other branches. RHEL 10 systems will see the version of ramalama in the repos as a downgrade after they upgrade from RHEL 10.0 to 10.1. Version-Release number of selected component (if applicable): epel10.0: ramalama-0.13.0-1.el10_0 epel10.1: ramalama-0.12.0-1.el10_1 epel10.2: ramalama-0.13.0-1.el10_2 How reproducible: always Steps to Reproduce: 1. install ramalama on RHEL 10.0 2. upgrade to RHEL 10.1 3. dnf distrosync Actual results: ramalama is downgraded Expected results: ramalama is unchanged or upgraded Additional info: EPEL policy requires that packages have a valid upgrade path between minor versions. https://docs.fedoraproject.org/en-US/epel/epel-policy/#upgrade_path_policy I've submitted a PR to remove epel10.0 from the Packit configuration as it will be retired soon. I didn't merely switch it to epel10.1 so this problem can be avoided in the future. https://src.fedoraproject.org/rpms/ramalama/pull-request/52