system-config-services seems to have in it: Obsoletes: system-config-services < 0.99.29 Conflicts: system-config-services < 0.99.29 Is there any reason for this? I am having trouble thinking of any reason a package should obsolete and conflict with an eariler version of itself. If it's newer it would just upgrade.
The conflicts line is indeed bogus (now that you got me thinking about it). I've committed this spec file comment to the upstream git repository explaining the rationale for this obsoletes line: # Until version 0.99.28, system-config-date contained online documentation. # From version 0.99.29 on, online documentation is split off into its own # package system-config-services-docs. The following ensures that updating from # earlier versions gives you both the main package and documentation. Obsoletes: system-config-services < 0.99.29