Currently, fedup to 21 fails unless --instrepo is explicitly specified, because the 'fedora-install-21' repo does not exist in mirrormanager. fedup looks for:
If I understood him correctly, Dennis told me we actually can't fix this as easily as you'd think, because for some reason we can't have two mirrormanager 'repos' pointing to the same place, but to fix this we'd want to have both fedora-server-21 and fedora-install-21 pointing to:
so in a weird way, this actually depends on https://bugzilla.redhat.com/show_bug.cgi?id=1128474 .
Dennis, might it be possible to do something a bit hacky like point fedora-server-21 at Beta and fedora-install-21 at Final TC1? it's not entirely 'correct' but it shouldn't really break too badly. Once we have a TC2 we could fiddle it around a bit more. Once we fix #1128474 we could leave fedora-server-21 pointing at whatever the last compose was that needed a Product-specific repo, and keep fedora-install-21 pointing at the latest compose (or at TC1 if we want to be sure it's pointed at something 'safe', and use --instrepo for testing the latest compose).
Proposing as a Final blocker:
"For each one of the release-blocking package sets, it must be possible to successfully complete an upgrade from a fully updated installation of the previous stable Fedora release with that package set installed. The user must be made to specify which Product (or none) they wish to have running when upgrade is complete."
*** Bug 1161464 has been marked as a duplicate of this bug. ***
releng fixed this up a couple of days ago, I think we're currently using something like my suggestion in the description.
http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-install-21&arch=x86_64 works correctly and I just tried `fedup --network 21 --product workstation` from F20 and it works well. Closing as fixed.