Bug 2249679

Summary:	Changes/SQLAlchemy 2
Product:	[Fedora] Fedora	Reporter:	Aoife Moloney <amoloney>
Component:	Changes Tracking	Assignee:	Nils Philippsen <nphilipp>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	40	CC:	amoloney, awilliam, ckalina, nphilipp, upstream-release-monitoring
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:	2024-04-29 09:29: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:	2105403, 2181303

Description Aoife Moloney 2023-11-14 19:54:12 UTC

This is a tracking bug for Change: Changes/SQLAlchemy 2
For more details, see: https://fedoraproject.org/wiki/Changes/SQLAlchemy_2

The python-sqlalchemy package is upgraded to major version 2. A compatibility package python-sqlalchemy1.4 is added to the distribution to cater for software which doesn’t yet use the new API, this can be installed alternatively. Other packages using SQLAlchemy are identified and, if necessary, steps are taken to ensure they use the correct major version package.

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 Nils Philippsen 2024-01-19 13:19:05 UTC

*** Bug 2134559 has been marked as a duplicate of this bug. ***

Comment 2 Aoife Moloney 2024-02-19 17:23:46 UTC

Hi Nils!

Im doing a check in on all F0 changes now that were passed the Testable deadline and heading for the 100% complete one to make sure theres a good understanding of what changes are on track, and what ones might be slipping a little. How is the upgrade to SQL Alchemy 2 coming along?


Thanks,
Aoife

Comment 3 Adam Williamson 2024-02-21 06:21:47 UTC

Well, we at least have python-sqlalchemy-2.0.27-1.fc40 and python-sqlalchemy1.4-1.4.51-1.fc40 tagged, so the core of the Change is done. I'm not sure about the other elements in the scope, but I think we can call this MODIFIED at least.

Comment 4 Nils Philippsen 2024-03-25 21:09:25 UTC

(In reply to Aoife Moloney from comment #2)
> Im doing a check in on all F0 changes now that were passed the Testable
> deadline and heading for the 100% complete one to make sure theres a good
> understanding of what changes are on track, and what ones might be slipping
> a little. How is the upgrade to SQL Alchemy 2 coming along?

Hi Aoife!

Sorry it took me so long to reply… As Adam said, both the new version and the compat package have been in for a while.

In the meantime, I’ve worked through the long list of packages using SQLAlchemy and added tighter version requirement where I found they were missing, so I would call this change complete.

Comment 5 Aoife Moloney 2024-04-29 09:29:27 UTC

F40 was released on 2024-04-23, so I am closing this tracker. If this Change was not completed, please notify me ASAP.