Created attachment 1328009 [details] Reproducing SRPM Description of problem: If a noarch subpackage contains some metainfo/appdata, builds *always* fail on F27, due to rpmdiff errors. Steps to Reproduce: 1. See attached SRPM that exhibits the problem: test-breakage-1-1.fc28.src.rpm 2. Attempt to build it in a F27 koji scratch build The build will fail with the following error on F27 only: removed PROVIDES metainfo(/builddir/build/BUILDROOT/test-breakage-1-1.fc27.x86_64/usr/share/appdata/eclipse-jdt.metainfo.xml) added PROVIDES metainfo(/builddir/build/BUILDROOT/test-breakage-1-1.fc27.ppc64le/usr/share/appdata/eclipse-jdt.metainfo.xml) See this example F27 scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=21971097 However the very same SRPM builds successfully on both F26 and F28. See these example F26 and F28 scratch builds: https://koji.fedoraproject.org/koji/taskinfo?taskID=21971090 https://koji.fedoraproject.org/koji/taskinfo?taskID=21971106 This appears to be because incorrect provides are being generated in the F27 case. Consider the difference in the provides list that RPM generates between F27 and F28: $ rpm -qp --provides test-breakage-jdt-1-1.fc27.noarch.rpm metainfo() metainfo(/builddir/build/BUILDROOT/test-breakage-1-1.fc27.x86_64/usr/share/appdata/eclipse-jdt.metainfo.xml) test-breakage-jdt = 1-1.fc27 $ rpm -qp --provides test-breakage-jdt-1-1.fc28.noarch.rpm metainfo() metainfo(eclipse-jdt.metainfo.xml) test-breakage-jdt = 1-1.fc28 As you can see, the F27 version has erroneously included the full buildroot path in the metainfo() provide. This makes it impossible to include appdata in noarch packages built for F27.
I originally reported this to releng here: https://pagure.io/releng/issue/7037 And was advised to file a bug against RPM
Proposed as a Blocker for 27-final by Fedora user mbooth using the blocker tracking app because: Makes it impossible build some packages with full appstream metainfo, meaning that at GA, some applications will not be discoverable through gnome-software. This will affect (at the very least) users of Eclipse IDE and it's plugins.
*** This bug has been marked as a duplicate of bug 1483644 ***