Bug 2171470

Summary:	dlrn: FTBFS in Fedora rawhide/f38
Product:	[Fedora] Fedora	Reporter:	Fedora Release Engineering <releng>
Component:	dlrn	Assignee:	Orphan Owner <extras-orphan>
Status:	ASSIGNED ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	39	CC:	amoralej, jpena, openstack-sig
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:		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:	2117176

Description Fedora Release Engineering 2023-02-20 11:46:31 UTC

dlrn failed to build from source in Fedora rawhide/f38

https://koji.fedoraproject.org/koji/taskinfo?taskID=96321218


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
Please fix dlrn at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
dlrn will be orphaned. Before branching of Fedora 39,
dlrn will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

Comment 1 Alfredo Moralejo 2023-03-08 16:24:48 UTC

In addition to the issue with the unit tests and the version of python-sh in fedora, we need to check if fedora is providing all the dependencies for latest release, some deps were added for the API after current version in fedora. With that we can evaluate the required effort and the value of maintaining it in Fedora.

Comment 2 Javier Peña 2023-03-08 17:03:39 UTC

If I remember correctly, the biggest issue to update the DLRN version in RPM was the python-graphene and python-graphene-sqlalchemy versions. I think the process should be:

- Test DLRN with graphene > 3.0 and graphene-sqlalchemy > 3.0.0b1
- Once that is done, update the python-graphene RPM, unretire & update python-graphene-sqlalchemy
- Finally, update the DLRN rpm.

Back in 2021, we did not have a tag for graphene-sqlalchemy that allowed us to use it in combination with graphene 3.0.

Comment 3 Fedora Admin user for bugzilla script actions 2023-07-14 00:06:46 UTC

This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 4 Fedora Release Engineering 2023-08-16 07:07:34 UTC

This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.