On Mon, Dec 28, 2015 at 10:00 AM, Parag Nemade panemade@gmail.com wrote:
Hi,
On Sun, Dec 27, 2015 at 8:19 PM, Piotr Popieluch piotr1212@gmail.com wrote:
On 12/23/2015 09:13 PM, Jason L Tibbitts III wrote:
I've been working on an epel-rpm-macros package for EL6. It doesn't do much at the moment, but in order to make sure it doesn't break things I wanted to be able to do a complete rebuild of all of the EPEL6 packages.
So I've written some scripts and stolen CPU from a few hosts. I still have more hosts to add to the pool, but I can currently rebuild all 5700+ packages in a couple of hours.
Unfortunately I found more failures than expected: 195. The mock logs from the failures are at: http://www.math.uh.edu/~tibbs/fedora/mass-rebuild-epel6-20151223/
<< snip >>
The following have unsatisfied dependencies. I suppose they should be retired:
<< snip >>
nodejs-ascii-tree-0.1.1-1.el6.src.rpm nodejs-nsp-audit-shrinkwrap-1.0.2-1.el6.src.rpm nodejs-rc-0.5.4-2.el6.src.rpm nodejs-registry-url-2.0.0-2.el6.src.rpm nodejs-seq-0.3.5-3.el6.src.rpm nodejs-silent-npm-registry-client-0.0.1-1.el6.src.rpm nodejs-stream-spigot-3.0.4-1.el6.src.rpm
Why do these packages failed to rebuild? I see they are asking for some packages missing in their root.log file but then how can they got initially built successfully?
I tried to just scratch-build nodejs-stream-spigot and it did not fail. Then I tried all above scratch-builds and found only failure for nodejs-ascii-tree, nodejs-rc, nodejs-registry-url. The last two failed because I don't know how but nodejs-strip-json-comments is not available in el6. I am not sure how it got untagged. I have now tagged and requested this package in EL6 testing.
Could there have been some change in how ExclusiveArch is handled?
I've had a package in the el6 repo, statsd, which disappeared magically from the el6 repo. This happened somewhere Q1/Q2 2015. Co-maintainer noticed that "ExclusiveArch: %{nodejs_arches} noarch" was being used while this macros is empty on el6. He updated it to use the correct arches and that solved the issue.
I still don't understand why it did work initially, but it might be the same reason as happening here?
Regards,
Piotr
These packages (and I expect their dependencies) use the %{nodejs_arches} macro, which is unavailable in el6.
I expect that if you add %{nodejs_arches} to the epel-rpm-macros package this will solve the issues.
Could you also add %{nodejs_find_provides_and_requires}?
Both macros are needed for nodejs packages on el6 only.
Yes good to add these macros.
Regards, Parag. _______________________________________________ epel-devel mailing list epel-devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.or...