Bug #4733

RPM feeds don't have conflicts between nightly/latest/next

Added by laforge 5 months ago. Updated about 6 hours ago.

In Progress
Target version:
Start date:
Due date:
% Done:


Spec Reference:


For the Debian package feeds, we have a mechanism in place that marks nightly conflicting with latest and next, and vice-versa. This is implemented in the osmo_obs_prepare_conflict shell function of

This mechanism is missing from the RPM builds (it apparently was forgotten when adding RPM packages), which makes it easy to run incompatible versions of programs/libraries.

We need to replicate this for RPM based distributions like CentOS.


#1 Updated by laforge 5 months ago

  • Priority changed from Normal to Low

#2 Updated by pespin about 1 month ago

  • Assignee changed from pespin to osmith

#3 Updated by osmith 4 days ago

  • Status changed from New to In Progress
  • Priority changed from Low to High

#4 Updated by osmith 3 days ago

  • % Done changed from 0 to 60

I've added a the dummy package for rpm. As discussed, I've also made all packages of nightly and next depend on a specific version of the dummy package (so one can't mix packages from different dates by accident).

Done is at 60% now, because I'd like to extend repo-install-test to continuously test that the conflicts work as intended. From manual testing, it appears to be working as expected.

#5 Updated by osmith about 6 hours ago

  • % Done changed from 60 to 70

Previous patches are merged and rolled out. The RPM packages are built for both CentOS and openSUSE, and for the latter, rpmlint started to complain about libraries depending on specific versions of packages. This is desired in our use case (for nightly and next feeds), so I've added a patch to make the error non-fatal:

#6 Updated by osmith about 6 hours ago

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)