RPM version goes backward in Rawhide

[Garrett Holmstrom]

On 2011-08-19 20:41, Kevin Kofler wrote:
> Updates can be pulled out of updates-testing at any moment, which makes a
> lot of sense, but which means that users with updates-testing enabled will
> end up with the EVR going backwards, something that's not even allowed in
> Rawhide.
>
> Enabling updates-testing by default means forcing EVR downgrades on users of
> Branched by default, making the policy banning them in Rawhide totally
> pointless.

> The problem is that basically nobody is testing the actual release package
> set, considering that it's much less straightforward to opt out of updates-
> testing than to opt in, and that probably only few people are doing it (and
> those who do bother to explicitly opt out of updates-testing are the ones
> who just need early access to the releases for whatever reason, e.g. because
> they need a newer version of some package, and don't actually want to do any
> testing whatsoever, just to seamlessly move on to the release when it's out
> officially).

FESCo discussed both of these issues before the release of the Fedora 15 
Alpha at its meetings on 16 Feb 2011 and 2 Mar 2011.  The current 
recommendation [1] is to run ``yum distro-sync'' after upgrading from 
pre-releases to the final release.

[1] 
https://fedoraproject.org/wiki/Upgrading_from_pre-release_to_final#After_updating_to_final.2C_why_does_yum_complain_about_mismatched_package_versions_even_though_my_rawhide_repo_is_disabled.3F