Bug 1270602

Summary:	qtwebkit-5.5.1 no longer defines QTWEBKIT_VERSION_CHECK macro
Product:	[Fedora] Fedora	Reporter:	Raphael Groner <projects.rg>
Component:	qt5-qtwebkit	Assignee:	Than Ngo <than>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	christoph.wickert, helio, jgrulich, jreznik, kevin, ltinkl, rdieter, rnovacek, than
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	https://apps.fedoraproject.org/koschei/package/qupzilla
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-12 16:04:28 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:

Description Raphael Groner 2015-10-11 18:13:36 UTC

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

Version-Release number of selected component (if applicable):
1.8.6-7.fc24

Steps to Reproduce:
koji build --scratch f24 qupzilla-1.8.6-7.fc24.src.rpm

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

This seems to be related to some incomplete qtwebkit header cause of the failing macro QTWEBKIT_VERSION_CHECK.

Comment 1 Raphael Groner 2015-10-11 18:14:34 UTC

http://koji.fedoraproject.org/koji/taskinfo?taskID=11397972

Comment 2 Rex Dieter 2015-10-12 12:53:10 UTC

qupzilla:

%changelog
* Mon Oct 12 2015 Rex Dieter <rdieter> 1.8.7-2
- workaroung qtwebkit-5.5.1 dropping QTWEBKIT_VERSION_CHECK macro (#1270602)


In the meantime, will poke qtwebkit upstream to verify if this (arguably incompatible) change was intentional.

Comment 3 Rex Dieter 2015-10-12 16:04:28 UTC

Looks like removal was on purpose,

http://code.qt.io/cgit/qt/qtwebkit.git/commit/?h=5.5&id=c3e58209d3601d86eeacde7abeeb39eb67a5aaf3

I'd suggest poking qupzilla upstream about this issue, they can either take the workaround patch I made, or come up with some better solution