Learn more about these different git repos.
Other Git URLs
We could now use a Final candidate build. It would be good to have a compose with the blocker-fixing selinux-policy and systemd updates to test before pushing them stable.
Please include:
I guess at this point we have to decide whether we use the 'RC' productmd milestone or what, we never did quite settle that...
Well we couldn't do a non-RC candidate for $REASONS, but we are ready for an RC now, so can we please have one?
Please make sure to compose with [https://admin.fedoraproject.org/updates/FEDORA-2016-aa49938267 pungi-4.0.15-2.fc24] to ensure we don't hit [https://bugzilla.redhat.com/show_bug.cgi?id=1331317 #1331317]. You may also choose to compose with [https://admin.fedoraproject.org/updates/FEDORA-2016-41bde7479f lorax-24.19-1.fc24] to address FE [https://bugzilla.redhat.com/show_bug.cgi?id=1342289 #1342289].
== Blocker ==
== FE ==
(that's a lot of FEs, but many of them are just FTBFS/dependency fixes in non-critical packages, so pretty safe).
ah, shit, we're gonna need a bumped spin-kickstarts aren't we? I'll get on that.
https://bugzilla.redhat.com/show_bug.cgi?id=1344812 is the spin-kickstarts bug, we probably should wait for that before doing the RC...
I'll get a build from the f24 branch of fedora-kickstarts done shortly barring problems. In the past we were waiting for Gold before doing the build. Is the order change due to the new compose process?
I did a build using 03020f4a748e0616dc3968e2e1afbfd72b33b057 provisionally tagged 0.24.4. I can't push tags so someone should do that. I also can't publish the tar ball on fedora-kickstarts and the old fedorahosted site is locked. I also didn't change the source url in the spec file, which we will want to point to the new location, https://bodhi.fedoraproject.org/updates/FEDORA-2016-fccb102356
I added you to the pagure project so you should be able to push your tag and upload the source now. ;)
We will need to sort out the names differences and such, but after f24 I think for that. ;)
I uploaded a copy of the release tar ball.
I had meant to say I didn't want to worry about the name change until f25.
I am still not able to clone using an ssh url. I can scp in to fedorapeople.org, so my public ssh key is likely correct. On my end it does appear to be using the correct identity file for pagure.io, but public key authentication is failing. So I haven't pushed the tag yet. That isn't that critical right now and I'll see about getting some pagure help for this.
I figured out my problem and pushed the tag.
OK, so we have a spin-kickstarts build. Please do the RC with all stuff from comment 2 and [https://bodhi.fedoraproject.org/updates/FEDORA-2016-fccb102356 spin-kickstarts-0.24.4-1.fc24] for [https://bugzilla.redhat.com/show_bug.cgi?id=1344812 #1344812] (let's just go ahead and assume it'll be an accepted blocker, we all know it will).
Compose is done at https://kojipkgs.fedoraproject.org/compose/24/Fedora-24-20160611.1/ and is synced to http://dl.fedoraproject.org/pub/alt/stage/24-1.1/ there is one possible issue, the install media hs _RC in its name
Re-opening for RC2. Please DO NOT include qt-virt-manager-0.27.50-4.fc24 this time - please un-tag it or whatever you have to do to not include it (the hadoop / nc6 update should negate the need for that one).
In addition to the includes and build-withs from RC1, please include the following:
Compose is done and available at https://kojipkgs.fedoraproject.org/compose/24/Fedora-24-20160614.0/ and http://alt.fedoraproject.org/pub/alt/stage/24_RC-1.2/
Metadata Update from @adamwill: - Issue set to the milestone: Fedora 24 Final
Login to comment on this ticket.