In current F33 repos (and F33 RC 1.1 compose), there is fedora-release-common-33-0.15.noarch, which means it doesn't have 1.0 version. Our OpenQA test claims that's invalid: > # Test died: RC candidate or update compose should not have 0.x versioned fedora-release! at /var/lib/openqa/share/tests/fedora/tests/os_release.pm line 108. https://openqa.fedoraproject.org/tests/694483#step/os_release/6 I'm not sure whether this is a hard blocker or not (from the releng PoV), but proposing as one.
This might actually cause bug 1888202
Does it make sense to close this as a duplicate of 1888202 for easier tracking, etc?
I'm inquiring at #anaconda whether this really is the root cause for bug 1888202
(In reply to Kamil Páral from comment #3) > I'm inquiring at #anaconda whether this really is the root cause for bug > 1888202 Yes, anaconda has a check for that, we also need a 33-1 build to turn off updates-testing and not install the -rawhide repos by default as per standard release criteria
FEDORA-2020-941b0d5a2e has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-941b0d5a2e
RELEASE=$(rpm -q --qf '%{Release}' --whatprovides system-release) if [ "${RELEASE:0:2}" = "0." ]; then export ANACONDA_ISFINAL="false" else export ANACONDA_ISFINAL="true" fi https://github.com/rhinstaller/anaconda/blob/master/data/liveinst/liveinst#L66
(In reply to Fedora Update System from comment #5) > FEDORA-2020-941b0d5a2e has been submitted as an update to Fedora 33. > https://bodhi.fedoraproject.org/updates/FEDORA-2020-941b0d5a2e Tested.
FEDORA-2020-941b0d5a2e has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-941b0d5a2e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-941b0d5a2e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
*** Bug 1888202 has been marked as a duplicate of this bug. ***
Criteria here are: "No notices or alerts about pre-release status may be shown as part of installation or critical path actions on release-blocking desktops" (without final fedora-release, we get pre-release messages on lives) "A fedora-release package containing the correct names, information and repository configuration for a final Fedora release must be present on release-blocking images and the appropriately versioned generic-release package must be available in the release repository" (without final fedora-repos, we have updates-testing enabled by default) We need to update that second criterion to reference fedora-repos, I think.
The decision to classify this bug as an "AcceptedBlocker (Final)" was made. [0] [0] https://pagure.io/fedora-qa/blocker-review/issue/169
so close... why would we use the same text for bugzilla and the voting app, that would be way too easy
FEDORA-2020-941b0d5a2e has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.