What happened to packages in updates-testing?

[dd_wizard]

Since I upgraded to F13 from F12, I've been watching for orphaned packages with yum list extras. Up until today, the list has been small and stable. The list was made up of things I installed from koji, or packages like alsa-lib that were updated in F12 after they were built for F13. Today, a number of packages that came from updates-testing now show up as extras. After checking koji, it appears that a lot of packages were pulled from updates-testing since yesterday. The new extra packages are:
autocorr-en.noarch 1:3.2.0-12.10.fc13 @updates-testing
clutter.x86_64 1.2.0-1.fc13 @updates-testing
gegl.x86_64 0.1.2-2.fc13 @updates-testing
gimp.x86_64 2:2.6.8-5.fc13 @updates-testing
gimp-help-browser.x86_64 2:2.6.8-5.fc13 @updates-testing
gimp-libs.x86_64 2:2.6.8-5.fc13 @updates-testing
gir-repository.x86_64 0.6.5-6.fc13 @updates-testing
gupnp.x86_64 0.13.2-2.fc13 @updates-testing
hunspell.x86_64 1.2.8-17.fc13 @updates-testing
libgtop2.x86_64 2.28.0-2.fc13 @updates-testing
openoffice.org-brand.x86_64 1:3.2.0-12.10.fc13 @updates-testing
openoffice.org-calc.x86_64 1:3.2.0-12.10.fc13 @updates-testing
openoffice.org-calc-core.x86_64 1:3.2.0-12.10.fc13 @updates-testing
openoffice.org-core.x86_64 1:3.2.0-12.10.fc13 @updates-testing
openoffice.org-draw.x86_64 1:3.2.0-12.10.fc13 @updates-testing
openoffice.org-draw-core.x86_64 1:3.2.0-12.10.fc13 @updates-testing
openoffice.org-graphicfilter.x86_64 1:3.2.0-12.10.fc13 @updates-testing
openoffice.org-math.x86_64 1:3.2.0-12.10.fc13 @updates-testing
openoffice.org-math-core.x86_64 1:3.2.0-12.10.fc13 @updates-testing
openoffice.org-opensymbol-fonts.noarch 1:3.2.0-12.10.fc13 @updates-testing
openoffice.org-pdfimport.x86_64 1:3.2.0-12.10.fc13 @updates-testing
openoffice.org-ure.x86_64 1:3.2.0-12.10.fc13 @updates-testing
openoffice.org-writer.x86_64 1:3.2.0-12.10.fc13 @updates-testing
openoffice.org-writer-core.x86_64 1:3.2.0-12.10.fc13 @updates-testing
qbittorrent.x86_64 2.2.0-0.10.rc1.fc13 @updates-testing
tokyocabinet.x86_64 1.4.42-1.fc13 @updates-testing
What's up with that? And is a downgrade a good idea for the affected packages?

dd_wizard

---------- Post added at 12:59 PM CST ---------- Previous post was at 12:57 PM CST ----------

I just realized they may have moved to updates since it's alpha release, but enabling updates gives the same list.

dd_wizard

---------- Post added at 03:54 PM CST ---------- Previous post was at 12:59 PM CST ----------

NM, I just did an update, and lo and behold, the missing packages are back on updates-testing. Maybe a mirror issue?

dd_wizard

[jff]

Updates seems to be broken in F13 Alpha. Yesterday I got an error "Public key for sos-1.9-1.fc12.noarch.rpm is not installed "(http://osdir.com/ml/general/2010-03/msg12713.html). Now there's dependency issues with openoffice.org packages. And for example thunderbird-3.0.3 is not available (for F12 it is).

[l815]

Updates seems to be broken in F13 Alpha. Yesterday I got an error "Public key for sos-1.9-1.fc12.noarch.rpm is not installed "(http://osdir.com/ml/general/2010-03/msg12713.html). Now there's dependency issues with openoffice.org packages. And for example thunderbird-3.0.3 is not available (for F12 it is).

Same here. I ended up just removing the sos package as well as open office, which after worked fine.

[GoinEasy9]

yum --nogpgcheck update would have solved the problem.

Since installing F13, fedora.repo and updates-testing.repo have been enabled. Unless something has changed fedora-updates.repo is still empty.

[Demz]

yum --nogpgcheck update would have solved the problem.

Since installing F13, fedora.repo and updates-testing.repo have been enabled. Unless something has changed fedora-updates.repo is still empty.

why do people think that repo is still Empty? its plain obvious why its empty

[GoinEasy9]

why do people think that repo is still Empty? its plain obvious why its empty

I don't think the obvious works all the time in Fedora. When F12 was released, the kernel it was released with was still in the updates-testing repo, which was disabled by default. To me, it would have been obvious that it would have been included in the fedora.repo. So when I did yum install kernel-devel I got the version for the previous kernel, from when it was still beta. It took a little while for me to figure out that the wrong version was installed, because obviously that shouldn't have happened, causing me to clean up my Nvidia blob install, and start over with updates testing enabled.
Was it obvious that the rawhide repos would be split into F13 and a non-frozen rawhide repo?
Not to argue, but, when I say "Unless something has changed", I'm going by my less than one year experience with Fedora, and that leaves me with "Nothing is obvious".

[CiaW]

I've had dep-solving issues ever since I installed the pre-alpha, so I'm now in the habit of using --skip-broken. gegl has been one of the 'broken' the whole time... I figured it'll get resolved eventually.

[dd_wizard]

Gegl was broken a while ago, so I pulled it from koji. But I see my current version came from updates-testing, so maybe it's fixed now. Iirc, gimp deps were broken for me, that's what kept gegl from installing.

dd_wizard

[GoinEasy9]

I don't have the broken gegl anymore, it was fixed when a new version of Gimp came in, geez, about a week ago. I did remove yum-langpacks though, it was holding OpenOffice from getting updated. Today I did updates of both F13 and Rawhide and was able to get through both with just yum update. That's the first time I was able to do that since getting F13 installed a couple of weeks ago.

[newiLuvatar]

I did remove yum-langpacks though, it was holding OpenOffice from getting updated.
same here...