On Sun, 2016-11-20 at 14:05 -0500, Neal Becker wrote: > I tried to test upgrade f24->f25: > > sudo dnf system-upgrade download --refresh --releasever=25 -- > allowerasing > > but it wanted to downgrade a large number of packages, particularly > texlive: > [hundreds of downgrades...] > texlive-zlmtt noarch > 5:svn34485.1.01- > 17.fc25.1 fedora > 35 k > > Just checking that last one: > rpm -q texlive-zlmtt > texlive-zlmtt-svn34485.1.01-24.fc24.1.noarch > > Yup, the f24 version seems to be newer. > > I suppose this is not the correct procedure? Well, no. There really isn't any bug here. The current F25 package is older than the current F24 package, so if you upgrade from F24 to F25, the package will indeed be downgraded. This is all basically as it should be, nothing is wrong, and if you went ahead with the upgrade, it ought to work correctly. This is not uncommon around this point in the cycle, because updates can be pushed stable for 23 and 24 while 25 is in its Final freeze and only blocker / FE fixes can be pushed stable. So it does happen that 25 'stable' gets behind 23/24 'stable' for some packages. This usually gets sorted out when we start doing the post-freeze stable pushes, but it's usually not actually a *problem* anyway. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
