Bug 2233274

Summary:	Golang 1.21
Product:	[Fedora] Fedora	Reporter:	Adam Williamson <awilliam>
Component:	Changes Tracking	Assignee:	Alejandro Sáez Morollón <asm>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	asm
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-11-14 18:57:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2158243

Description Adam Williamson 2023-08-21 19:40:30 UTC

This is a tracking bug for Change: Golang 1.21
For more details, see: https://fedoraproject.org/wiki/Changes/golang1.21

Update of Go (golang package) to the upcoming version 1.21 in Fedora 39.

If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.

Comment 1 Adam Williamson 2023-08-21 21:26:16 UTC

So, Go 1.21 seems to be tagged in F39: https://bodhi.fedoraproject.org/updates/FEDORA-2023-0b607824d3 (and then a couple of later builds). However, I don't see any record of the "mass rebuild of all of the dependent packages" that the Change page says would be "required". What's going on with that? Not sure if this should be ASSIGNED, MODIFIED or ON_QA given the uncertainty.

Comment 2 Adam Williamson 2023-08-21 21:28:12 UTC

ah, looking closer, I think it mostly happened as part of the general mass rebuild; seems we had Go 1.21~rc3 tagged at that point.

Marking as ON_QA. It does look like at least some packages failed the mass rebuild, though, e.g golang-google-protobuf - several can be seen in https://koji.fedoraproject.org/koji/userinfo?buildStart=10&userID=4521&buildOrder=-completion_time&packageOrder=package_name&packageStart=0#buildlist . Are those being taken care of?

Comment 3 Alejandro Sáez Morollón 2023-09-06 15:23:33 UTC

Yes, I was able to update to ~rc3 at that point in time (now F39 should have the latest stable version). I guess this can be considered done.

Regarding the packages, the Go SIG is working on fixing some of the failing packages as a shared effort. Not sure if that answer your question.

Comment 4 Aoife Moloney 2023-11-14 18:57:27 UTC

F39 was released on November 7th, so I am closing this tracker. If this Change was not completed, please notify me ASAP.