#7037 Unable to complete build of Eclipse on F27
Closed: Can't Fix Opened by mbooth.

Builds of Eclipse on F27 fail to complete, see:

https://koji.fedoraproject.org/koji/taskinfo?taskID=21927075

The error seems to be:

BuildError: The following noarch package built differently on different architectures: eclipse-jdt-4.7.1-2.fc27.noarch.rpm
rpmdiff output was:
error: cannot open Packages index using db5 - Permission denied (13)
error: cannot open Packages database in /var/lib/rpm
error: cannot open Packages database in /var/lib/rpm

But build of the same git revision complete successfully on both F26 and F28, for example:

https://koji.fedoraproject.org/koji/taskinfo?taskID=21898079
https://koji.fedoraproject.org/koji/taskinfo?taskID=21898083

How can I fix this? And is it possible for the "failed" F27 build above to be tagged into the f27-updates-candidate?


Eclipse takes a looong time to build, so I want to avoid firing another build if possible

This is a bug in Fedora 27 RPM.
The "cannot open" errors are a red herring.
The actual problem is that RPM on F27 is injecting a PROVIDES with the full builddir in it: PROVIDES metainfo(/builddir/build/BUILDROOT/eclipse-4.7.0-4.fc27.aarch64/usr/share/appdata/eclipse-jdt.metainfo.xml).

This provides should have been something like: PROVIDES metainfo(/usr/share/appdata/eclipse-jdt.metainfo.xml).

Thanks for investigating. So for now, I will just avoid shipping appdata for this package and produce a simple reproduction case for a bug report on RPM.

Metadata Update from @puiterwijk:
- Issue close_status updated to: Can't Fix
- Issue status updated to: Closed (was: Open)

Seeing if this temporary workaround will allow my builds to complete:

http://pkgs.fedoraproject.org/cgit/rpms/eclipse.git/commit/?id=7ad9810339da53663777aa4daf7af9adad5b1a19

Metadata Update from @mbooth:
- Issue status updated to: Open (was: Closed)

@puiterwijk I filed a bug against RPM here: https://bugzilla.redhat.com/show_bug.cgi?id=1493204

@mbooth: thank you very much. I'll close this ticket.

Metadata Update from @puiterwijk:
- Issue close_status updated to: Can't Fix
- Issue status updated to: Closed (was: Open)

Metadata