See https://bugzilla.redhat.com/show_bug.cgi?id=1033250
Discussed at 2013-11-27 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-11-27/f20-blocker-review-3.2013-11-27-17.01.log.txt . Accepted as a freeze exception issue: this isn't critical but it can't be fixed post-release as it's about the installer's behaviour, and it would be good to fix things so people can change systemwide keyboard layouts post-install correctly. Mike's test gives us confidence that the change is correct.
vpodzime: can you push the fix to the 20 branch now it's accepted as FE? Thanks!
anaconda-20.25.13-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.25.13-1.fc20
Package anaconda-20.25.13-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-20.25.13-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-22666/anaconda-20.25.13-1.fc20 then log in and leave karma (feedback).
anaconda-20.25.14-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.25.14-1.fc20
So, I've just realized an unfortunate consequence of this change: I think we're going to break keymap in initramfs during fedup *again*, for yet *another* different reason. For F20-to-F21, not F19-to-F20. Filed as https://bugzilla.redhat.com/show_bug.cgi?id=1038413 .
anaconda-20.25.14-1.fc20, python-blivet-0.23.8-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.