Bug 360013

Summary: Applications/15.12 depends on 5.4.3 qt5
Product: [Applications] Artikulate Reporter: Scarlett Moore <sgmoore>
Component: generalAssignee: Andreas Cord-Landwehr <cordlandwehr>
Status: RESOLVED INTENTIONAL    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
URL: https://build-sandbox.kde.org/job/artikulate%20Applications-15.12%20stable-kf5-qt5/PLATFORM=Linux,compiler=gcc/4/console
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Scarlett Moore 2016-03-03 04:18:16 UTC 
Applications/15.12 depends on 5.4.3 qt5  as per kde-build-metadata all of Applications/15.12 depends on qt5 5.4.3. You bumped the dependency to 5.5 which should not happen unitl the 16.04 release cycle, leaving articulate in a failed state for stable.

Reproducible: Always

Steps to Reproduce:
1. build
2. fails
3.

Actual Results:  
Can't find qt5 5.5 and it never will in stable

Expected Results:  
Look for 5.4.3 like the rest of Applications/15.12

Please see http://anongit.kde.org/kde-build-metadata logical-module-structure for supported qt5 versions.
Comment 1 Andreas Cord-Landwehr 2016-03-03 08:21:48 UTC 
The hard build-dep was done before the dependency freeze of the 15.12 release. So I do not see any problem with it. As of now we do not have a global policy that defines the maximum Qt version one may depend on.
I agree that for convenience of the build system it would be good. But Artikulate hard depends on Qt 5.5. The major requirement is the QtQuick TreeView which was newly introduced in Qt 5.5. and porting away from it would be a major refactoring of the whole UI (not possible in a bugfix release). A smaller build dependency would work (e.g. 5.4, since ABI is compatible and the application would *only* crash at runtime), but to make this runtime-requirement obvious I want to keep it this way.
Comment 2 Scarlett Moore 2016-03-03 15:02:18 UTC 
I see. I was under the impression there was a policy. My apologies then. It will have to remain in a broken state until I sort out how to support divergence of applications with different qt versions. A complete rewrite I expect, so no time soon heh.