Since there have been some updates to the packages in the missing
repositories, and they're required by packages that the package manger
knows about, upgrading or installing packages is probably broken now
for most people.
i.e. doing "cap ec2onrails:server:upgrade_packages" will probably
break, and cap ec2onrails:server:install_packages" will break if one
of the new packages relies on a package in the missing repo.
See the bug report for more details and a workaround:
http://rubyforge.org/tracker/index.php?func=detail&aid=20040&group_id=4552&atid=17558
I know this probably affects a lot of people, sorry about that!
Paul