It seems the Fedora repo and the Updates Testing repo, but not the Updates repo, are enabled for F16 Alpha. What is strange is that I enabled Updates (and disabled Updates-Testing) and got a bunch of different updates from what is in Updates-Testing (which currently has broken deps).
/etc/yum.repos.d/fedora.repo:enabled=1 /etc/yum.repos.d/fedora.repo:enabled=0 /etc/yum.repos.d/fedora.repo:enabled=0 /etc/yum.repos.d/fedora-updates.repo:enabled=0 /etc/yum.repos.d/fedora-updates.repo:enabled=0 /etc/yum.repos.d/fedora-updates.repo:enabled=0 /etc/yum.repos.d/fedora-updates-testing.repo:enabled=1 /etc/yum.repos.d/fedora-updates-testing.repo:enabled=0 /etc/yum.repos.d/fedora-updates-testing.repo:enabled=0
I had to do this to get any Updates-Testing to install at all on x86_64:
yum --skip-broken update *.x86_64
The remaining updates that won't install are:
Packages skipped because of dependency problems: 1:control-center-3.1.5-1.fc16.x86_64 from updates-testing 1:control-center-filesystem-3.1.5-1.fc16.x86_64 from updates-testing empathy-3.1.5-1.fc16.x86_64 from updates-testing evolution-3.1.5-1.fc16.x86_64 from updates-testing evolution-NetworkManager-3.1.5-1.fc16.x86_64 from updates-testing evolution-data-server-3.1.5-1.fc16.x86_64 from updates-testing 1:folks-0.6.0-2.fc16.x86_64 from updates-testing gnome-contacts-0.1.2-1.fc16.x86_64 from updates-testing gnome-keyring-3.1.4-1.fc16.x86_64 from updates-testing gnome-keyring-pam-3.1.4-1.fc16.x86_64 from updates-testing gnome-panel-3.1.5-2.fc16.x86_64 from updates-testing libsocialweb-0.25.19-1.fc16.x86_64 from fedora libsocialweb-keys-0.25.19-1.fc16.noarch from fedora 1:nautilus-sendto-3.0.0-7.fc16.x86_64 from updates-testing p11-kit-0.3-2.fc16.x86_64 from fedora Error: Protected multilib versions: gnome-panel-libs-3.1.5-2.fc16.x86_64 != gnome-panel-libs-3.0.2-3.fc16.i686
On Sun, Aug 21, 2011 at 11:57:01 -0400, Chuck Anderson cra@WPI.EDU wrote:
It seems the Fedora repo and the Updates Testing repo, but not the Updates repo, are enabled for F16 Alpha. What is strange is that I enabled Updates (and disabled Updates-Testing) and got a bunch of different updates from what is in Updates-Testing (which currently has broken deps).
The updates repo is empty. That is normal for branched releases. Stuff goes from updates-testing into the rlease, rather than updates. There are some oddities of timing as the release doesn't get rebuilt at the same time as updates-testing. So that packages can disappear for a bit when moving from updates-testing to the release repo.