[EPEL-devel] Re: Mass rebuild of EPEL6 (2016-01-19)

[Parag Nemade]

Hi,

On Wed, Jan 20, 2016 at 9:46 AM, Jason L Tibbitts III  wrote:
> After spending far too much time playing with my mass rebuild script,
> and a whole lot of CPU time building packages, I've done another mass
> rebuild of EPEL6.  This involves an initial build of EPEL6 (with
> testing), another three builds of any failing packages, and then a final
> build of the current git of each failed package.  Packages which are
> excluded on x86_64 were skipped.
>
> The following packages are skipped because they take absolutely forever
> to build:
>
> elpa - Still building after two days on a rather fast machine!
> nwchem
> pypy
>
> This one's test suite appears to simply hang forever:
>
> rubygem-eventmachine
>
> Missing dependencies:
>
> dinotrace
> erlang-erlsom
> erlang-ibrowse
> freecad
> golang-github-endophage-gotuf
> golang-github-go-ldap-ldap
> golang-github-gonum-blas
> golang-github-gonum-floats
> golang-github-gorilla-sessions
> golang-github-hashicorp-serf
> golang-github-lsegal-gucumber
> golang-github-prometheus-client_golang
> golang-github-spf13-cast
> golang-github-spf13-viper
> gpredict
> jmtpfs
> nodejs-ascii-tree
> nodejs-duplexify
> nodejs-nsp-audit-shrinkwrap
> nodejs-nth-check
> nodejs-rc
> nodejs-registry-url
> nodejs-seq
> nodejs-silent-npm-registry-client
> nodejs-stream-spigot
> nodejs-test

I checked all above nodejs packages. I have already pushed
(epel-testing) most of them by replacing %{nodejs_arches} with its
actual definition and they are working fine. The only remaining
problematic package is nodejs-nsp-audit-shrinkwrap which I will get
fixed today. I am not sure about nodejs-nth-check which package needs
it.

Regards,
Parag.
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org

[EPEL-devel] Re: Mass rebuild of EPEL6

[Parag Nemade]

Hi,

On Sun, Dec 27, 2015 at 8:19 PM, Piotr Popieluch  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.

>
> 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.org