The rawhide policy is to not guarantee upgrade paths within rawhide
and/or the releases based on a rawhide snapshot.
The reason is that rawhide may try a newer package that may have to be
downgraded and one wants to avoid epoch inflation.
That's OK for rawhide, but what about "updates-testing"? Can we have
such a guarantee there?
--
Axel.Thimm at
ATrpms.net