Bug 1935578

Summary:	holland: FTBFS in Fedora rawhide
Product:	[Fedora] Fedora	Reporter:	Tomáš Hrnčiar <thrnciar>
Component:	holland	Assignee:	Jeffrey Ness <jeffrey.ness>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	ben.harper, dagofthedofg, jeffrey.ness, me, steven
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://koschei.fedoraproject.org/package/holland
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-03-27 13:58:15 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:	1890881, 1927309

Description Tomáš Hrnčiar 2021-03-05 08:15:29 UTC

Description of problem:
Package holland fails to build from source in Fedora rawhide.

Version-Release number of selected component (if applicable):
1.2.2-2.fc34

Steps to Reproduce:
koji build --scratch f35 holland-1.2.2-2.fc34.src.rpm

Additional info:
This package is tracked by Koschei. See:
https://koschei.fedoraproject.org/package/holland

RPM build errors:
+ cd holland-1.2.3
/var/tmp/rpm-tmp.lsEGdr: line 38: cd: holland-1.2.3: No such file or directory

Comment 1 Sam P 2021-03-08 20:08:18 UTC

Apologies for that. I had made a mistake while changing the source URL in the spec file when troubleshooting an issue in attempting to pull down the source tarball via spectool. The issue turned out to be a tagging mistake on the upstream project(V1.2.3 instead of v1.2.3) which when corrected allowed me to revert the source URL back to its previous value. I've pushed new builds for the targets that were impacted(everything but EPEL8) including rawhide and they show as building successfully. Thank you for catching this.