Learn more about these different git repos.
Other Git URLs
Describe the issue We need a side tag (f31-llvm) for the upcoming llvm rebase in Fedora
When do you need this? (YYYY/MM/DD) 07/29/2019
When is this no longer needed or useful? (YYYY/MM/DD) 08/29/2019
If we cannot complete your request, what is the impact? Temporary breakage in rawhide when the LLVM rebase occurs.
How many builds & for how long?
10 packages, and it can take 1 day or more to completely build all the packages.
Metadata Update from @ignatenkobrain: - Issue assigned to ignatenkobrain
Ok, I have created f31-llvm tag/target for you.
f31-llvm
Please wait until first newRepo will finish (about 15-30 minutes) and then you can build your packages there with fedpkg build --target=f31-llvm.
fedpkg build --target=f31-llvm
Metadata Update from @ignatenkobrain: - Issue tagged with: sidetarget
@tstellar Any update on this? We are branching tomorrow, it would be great if we can merge this side tag before branching.
Thanks.
I don't think I'm going to be ready before tomorrow. I'm still trying to debug some test failures in the clang package.
Can you merge this tag into rawhide? The builds are all ready.
All the builds are tagged into rawhide/f32.
Checking 9 builds... Tagging clang-9.0.0-0.2.rc3.fc31 into f32-pending Tagging clang8.0-8.0.0-3.fc31 into f32-pending Tagging compiler-rt-9.0.0-0.1.rc3.fc31 into f32-pending Tagging libomp-9.0.0-0.1.rc3.fc31 into f32-pending Tagging lld-9.0.0-0.1.rc3.fc31 into f32-pending Tagging lldb-9.0.0-0.1.rc3.fc31 into f32-pending Tagging llvm-9.0.0-0.4.rc3.fc31 into f32-pending Tagging llvm8.0-8.0.0-9.fc31 into f32-pending Tagging python-lit-0.9.0-0.1.rc4.fc31 into f32-pending Tagging 9 builds. Tagged 9 builds.
@tstellar Please re-open the ticket if you want us to tag into f31/branched as well?
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.