Forwarding to infra, TL;DR we seem to have an issue with rpmbuild (see below) and I'm not sure how to fix that, is there anyone who faced such issue in past? Vojtech ----- Forwarded Message ----- From: "Vojtech Szocs" <vszocs@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "Oved Ourfali" <oourfali@redhat.com>, "Alexander Wels" <awels@redhat.com>, "Greg Sheremeta" <gshereme@redhat.com>, "Juan Hernández" <jhernand@redhat.com>, "Ryan Barry" <rbarry@redhat.com> Sent: Monday, August 1, 2016 6:49:08 PM Subject: Errors / warnings in ovirt-engine-nodejs-modules build log Hi Sandro, I've looked into the build log [1]. Adding Juan & Ryan as well. Your feedback is highly appreciated. npm-specific issues (don't block the build): npm WARN package.json dependencies@ No repository field. npm WARN package.json dependencies@ No license field. - these warnings are harmless - TODO update modules' package.json npm WARN deprecated ... - some (possibly transitive) dependency in package.json relies on a deprecated npm package - TODO find out which dependencies are causing this npm ERR! registry error parsing json - this might indicate corrupt npm cache - should be fixed by `npm cache clean` - TODO update modules' build.sh npm WARN optional dep failed, continuing ... - these warnings are harmless - some (possibly transitive) dependency in package.json relies on an optional npm package that is platform-specific but it is NOT available for current platform - e.g. "fsevents" is MacOSX only - this should be fixed by `npm install --no-optional` - TODO update modules' build.sh sh: bower: command not found npm WARN optional dep failed, continuing bootstrap-treeview@1.2.0 - bootstrap-treeview does `bower install` in its `install` script - this is BAD practice (bootstrap-treeview's fault) - TODO latest commit on May 9, 2015 -- do we need this at all (?) CI-specific issues (which block the build): Wrote: /tmp/ovirt-engine-nodejs-modules/ovirt-engine-nodejs-modules-0.0.10-1.fc24.src.rpm error: Unable to create immutable header region. - at this point, spec's %install phase has finished executing and RPM was created - it is rpmbuild related, see https://bugzilla.redhat.com/show_bug.cgi?id=913099#c2 For ^^ error, seems like too many files in RPM package will cause "artificial cap on header size" to be exceeded and rpmbuild fails. Juan, what do you think? I don't have any idea how to solve this. I don't understand the actual issue as we're creating single .tar file from `node_modules` directory during the RPM build.. [1] http://jenkins.ovirt.org/job/ovirt-engine-nodejs-modules_master_create-rpms-... Thanks, Vojtech