Bug 2296176

Summary:	ocrmypdf FTBFS on the s390x architecture
Product:	[Fedora] Fedora	Reporter:	Ben Beasley <code>
Component:	ocrmypdf	Assignee:	Elliott Sales de Andrade <quantum.analyst>
Status:	NEW ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	42	CC:	python-packagers-sig, quantum.analyst
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
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:	485231

Description Ben Beasley 2024-07-07 12:17:12 UTC

On the big-endian s390x architecture, ocrmypdf fails to build from source because python3-img2pdf is not available:

No match for argument: python3dist(img2pdf) >= 0.4.4

This is a case of https://docs.fedoraproject.org/en-US/packaging-guidelines/#_noarch_with_unported_dependencies.

Blocking F-ExcludeArch-s390x per https://docs.fedoraproject.org/en-US/packaging-guidelines/#_architecture_build_failures.

It looks like python-img2pdf cites

  # cf. Bug 1851638 - img2pdf fails to build on s390x because of issues in the ImageMagick dependency
  # https://bugzilla.redhat.com/show_bug.cgi?id=1851638

for excluding s390x. I am not sure if this issue has been fixed or not; however, python-img2pdf currently FTBFS on F41 and F40 due to problems finding ICC profiles in the tests, and I did not have time to dig into it further.

For ocrmypdf, it would be best to either add

  # Unported dependency python-img2pdf (RHBZ#THISBUG)
  ExcludeArch:    s390x

or help fix python-img2pdf on s390x.

Comment 1 Aoife Moloney 2025-02-26 13:04:50 UTC

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