Description of problem:
Updates-testing repo needs to be disabled in Fedora 23 Final. It's still enabled. This blocks RC1 compose.
Version-Release number of selected component (if applicable):
This is a Final blocker, perhaps even an automatic one.
Discussed at 2015-10-05 blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2015-10-05/f23-blocker-review.2015-10-05-16.00.html . While we don't usually bother filing a blocker bug for this as it's usually taken care of as a matter of course by the relevant folks, this does technically meet the criteria, so since it's been filed, we accepted it as a blocker.
We're not asking for anything different from usual here - just that as usual a fedora-release that disables the updates-testing repo needs to be shipped at the appropriate point on the calendar (shortly before RC1 is composed, I guess).
fedora-repos-23-1 fedora-release-23-1 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-6656b35afd
fedora-release-23-1, fedora-repos-23-1 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update fedora-release fedora-repos'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-6656b35afd
I think this needs to be tagged to f23 for the GA Live images?
Okay nevermind sorry fedora-repos-23-1 is in RC2 and RC3.
Jens: if you want to follow the process, follow the TC/RC compose requests. 23 Final compose request ticket is:
as you can see, when we (QA) request a new TC/RC build, we list various packages that should be pulled into the compose to fix blocker/FE bugs, which have not yet made it to stable. These packages are pulled into a repo called 'bleed':
which is then included in the compose. In Spherical Cow Land this would never be necessary; the 'intended' process is that the updates are sent out, we test and karma them, push them to stable (manually, when freeze is in effect), and *then* compose, and the composes just contain whatever's in stable. But in practice, given Fedora's short schedules, we don't have time to wait for that process in all cases. And then there are things like lorax and anaconda updates where we need a compose before we can actually *test* the update and give it karma and push it stable (the catch-22 problem).
Hence, we have this little process.
Through the MAGIC OF COPY/PASTE, if you CC yourself on the current compose request ticket, you'll be CCed on all new ones for eternity (or until you un-CC yourself again, or me/whoever else creates the compose request ticket for a new milestone buggers up the copy/paste).
Updates-testing is disabled on RC3.
fedora-release-23-1, fedora-repos-23-1 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.