Bug 1759892

Summary:	ocrmypdf hangs in check phase of rpmbuild
Product:	[Fedora] Fedora	Reporter:	Zdenek Dohnal <zdohnal>
Component:	ocrmypdf	Assignee:	Elliott Sales de Andrade <quantum.analyst>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	python-sig, quantum.analyst
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ocrmypdf-9.0.5-1.fc32	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 06:04:09 UTC	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:	1747732

Description Zdenek Dohnal 2019-10-09 11:11:25 UTC

Description of problem:
The build of ocrmypdf hangs during %check. Please see the scratch build https://koji.fedoraproject.org/koji/taskinfo?taskID=38142769 or copr build https://copr.fedorainfracloud.org/coprs/zdohnal/qpdf/build/1044836/ .

Copr build was killed after 21 hours.


Steps to Reproduce:
1. fedpkg build --scratch --srpm


Additional info:
The bug blocks me on bug https://bugzilla.redhat.com/show_bug.cgi?id=1747732 - I would like to rebase qpdf, but ocrmypdf as dependent package is FTBFS even without new qpdf.

Comment 1 Elliott Sales de Andrade 2019-10-17 09:12:38 UTC

This is a known issue upstream and they simply disabled the stuck test. I would do the same, but it seems some other issue has arisen on Rawhide at least.

Are you rebasing on Rawhide only or elsewhere?

Comment 2 Zdenek Dohnal 2019-10-17 09:56:40 UTC

I would go with rawhide only for now. Maybe if a important fix will appear in newer qpdf, then I would go for rebase in stable branches.

Comment 3 Ben Cotton 2019-10-31 18:45:42 UTC

This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Elliott Sales de Andrade 2019-11-05 06:04:09 UTC

This seems to be fixed, though sometimes the build is a bit flaky.