Learn more about these different git repos.
Other Git URLs
@jcajka Sure, we can use the mass rebuild for rebuild, if any case golang1.15 is not landed before mass rebuild, you can request a side tag and we can use that to rebuild golang packages.
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open) - Issue tagged with: change-ack, changes, f33, mass rebuild
Metadata Update from @mohanboddu: - Issue status updated to: Open (was: Closed)
@mohanboddu Thanks. I plan to most probably go with pre-release version for mass-rebuild/rawhide and fix individual packages afterward, assuming no unexpected breakage, I don't expect need for side tag. If that works for rel-eng.
I'm currently running local rebuilds, got baseline over weekend.
Sure that works.
@jcajka Whats the status on this? I am still seeing golang-1.14 only.
@mohanboddu I will re-base later today to the pre-release beta1, I have been hoping that Google would cut rc1.
@mohanboddu done via https://koji.fedoraproject.org/koji/buildinfo?buildID=1544245
@mohanboddu I have just finished build of rc1 in rawhide https://koji.fedoraproject.org/koji/taskinfo?taskID=47916872 it would be good if that would be picked for mass-rebuild, but if it is already too late beta1 is just fine too.
@jcajka, I am going to run the rebuild in about 30mins. Will wait for your packages and run it after they land.
@humaton Awesome thanks :).
Closing the ticket as the work here is done.
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.