Please include the new fedora-release build that renames fedora-release-standard -> nonproduct in Fedora 21 Beta. It's a rather disruptive change, needs comps updates etc, but pulling it in now rather than after Beta makes sure we can properly test the upgrade path from F20. Fedup is going to have a hardcoded list of product names (server, workstation, cloud, nonproduct) and is going to give an option to choose between those 4 for F20 upgrades. Being able to rely on the new naming makes it possible to better test upgrades ahead of the final release. I'll link the build ID here once dgilmore has kicked off the new fedora-release build.
Proposed as a Blocker for 21-beta by Fedora user sgallagh using the blocker tracking app because: "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." (Proposed critertion in discussion) This fix must go in to enable the fedup changes to support this criterion.
+1 blocker, per c#1. Since we're going to have to do this, let's get it in ASAP - dgilmore and I will try to get it into TC4.
+1 blocker, but please please lets not paint the bikeshed anymore? ;)
+1 blocker
That's enough for acceptedblocker status, I'll list it in the TC4 request.
fedora-release-21-0.16 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/fedora-release-21-0.16
Package fedora-release-21-0.16: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fedora-release-21-0.16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-13090/fedora-release-21-0.16 then log in and leave karma (feedback).
Doesn't need to be a proposed FE if it's an acceptedblocker.
fedora-release-21-0.16 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
Problem still present in other place. While updating F20 -> F21 with tool "fedora-upgrade": ------------------------------------- ... some useless messages skipped ... What is your option? (cloud/server/workstation/standard) standard Resolving Dependencies --> Running transaction check ---> Package fedora-release-nonproduct.noarch 0:21-0.16 will be installed --> Processing Conflict: fedora-release-cloud-21-0.16.noarch conflicts fedora-release-nonproduct --> Processing Conflict: fedora-release-nonproduct-21-0.16.noarch conflicts fedora-release-cloud --> Finished Dependency Resolution Error: fedora-release-nonproduct conflicts with fedora-release-cloud-21-0.16.noarch Error: fedora-release-cloud conflicts with fedora-release-nonproduct-21-0.16.noarch You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
fedora-upgrade is not the standard, supported upgrade mechanism (that is fedup). Please file any bugs related to fedora-upgrade against its component.