Bug 368594

Summary:	kpackage_install_package macro sometimes fails to generate metainfo
Product:	[Frameworks and Libraries] frameworks-kpackage	Reporter:	Rex Dieter <rdieter>
Component:	default	Assignee:	Marco Martin <notmart>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Rex Dieter 2016-09-11 13:55:16 UTC

I've not been able to nail this down yet, but  kpackage_install_package macro  sometimes fails to generate metainfo with cmake output  similar to (using plasma-breeze as an example):

# CMake Warning at /usr/lib/cmake/KF5Package/KF5PackageMacros.cmake:45 (message):
# couldn't generate metainfo for org.kde.breezedark.desktop: Error: Can't
# find plugin metadata: /builddir/build/BUILD/breeze-5.7.4/lookandfeel.dark

Unfortunately, "Error: Can't find plugin metadata" is a bit too vague to help diagnose what's going wrong

Reproducible: Sometimes

Comment 1 Rex Dieter 2016-09-11 14:00:14 UTC

So far, I've seen it in 2 cases:

breeze: org.kde.breezedark.desktop.appdata.xml
plasma-sdk : org.kde.plasma.plasmoidviewershell.appdata.xml

since kf5-5.25 release (continues with recent 5.26)

Comment 2 Rex Dieter 2016-09-11 14:02:49 UTC

Here's the full cmake output for the breeze case (I patched kpackage macro to output the full kpackagetool5 command used):

-- /usr/bin/kpackagetool5 --appstream-metainfo /builddir/build/BUILD/breeze-5.7.4/lookandfeel.dark OUTPUT_FILE /builddir/build/BUILD/breeze-5.7.4/i686-redhat-linux-gnu/org.kde.breezedark.desktop.appdata.xml
CMake Warning at /usr/lib/cmake/KF5Package/KF5PackageMacros.cmake:46 (message):
  couldn't generate metainfo for org.kde.breezedark.desktop: Error: Can't
  find plugin metadata: /builddir/build/BUILD/breeze-5.7.4/lookandfeel.dark
Call Stack (most recent call first):
  CMakeLists.txt:40 (kpackage_install_package)

Comment 3 Rex Dieter 2016-09-11 14:04:44 UTC

marking a dup of bug #367923 , looks like same issue

*** This bug has been marked as a duplicate of bug 367923 ***