CentOS Digest, Vol 140, Issue 1

Home » CentOS » CentOS Digest, Vol 140, Issue 1
CentOS No Comments

Thanks Jim for responding.

I tried with mock configuration, but, not sure, i am still getting the same errors via repoclosre tool:-
This directory has got all the RPMs formed by mock.

[root@localhost YUM_CISCO_RPMS]# repoclosure -r Cisco-yum-dep-check Reading in repository metadata – please wait…. Checking Dependencies Repos looked at: 1
Cisco-yum-dep-check Num Packages in Repos: 1515
package: nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.CentOS.noarch from Cisco-yum-dep-check
unresolved deps:
nodejs010-npm(readable-stream) < 0:2 package: nodejs010-nodejs-cmd-shim-2.0.0-2.el7.CentOS.noarch from Cisco-yum-dep-check
unresolved deps:
nodejs010-npm(graceful-fs) < 0:4 package: nodejs010-nodejs-columnify-1.3.2-3.el7.CentOS.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(strip-ansi) >= 0:2.0.0
package: nodejs010-nodejs-fstream-ignore-1.0.2-1.el7.CentOS.noarch from Cisco-yum-dep-check
unresolved deps:
nodejs010-npm(minimatch) < 0:3 package: nodejs010-nodejs-gauge-1.2.2-3.el7.CentOS.noarch from Cisco-yum-dep-check
unresolved deps:
nodejs010-npm(has-unicode) < 0:2 package: nodejs010-nodejs-init-package-json-1.9.1-1.el7.CentOS.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(promzard) >= 0:0.3.0
package: nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.CentOS.noarch from Cisco-yum-dep-check
unresolved deps:
nodejs010-npm(retry) >= 0:0.8.0
nodejs010-npm(request) >= 0:2.47.0
nodejs010-npm(concat-stream) >= 0:1.4.6
package: nodejs010-nodejs-which-1.2.0-1.el7.CentOS.noarch from Cisco-yum-dep-check
unresolved deps:
nodejs010-npm(is-absolute) < 0:0.2 The only difference from my (for build of nodejs010-nodejs-which-1.2.0-1.el7.CentOS.noarch.rpm) build-log and http://cbs.CentOS.org/kojifiles/packages/nodejs010-nodejs-are-we-there-yet/1.0.4/1.el7/data/logs/noarch/build.log is following line:- *Requires: nodejs010-nodejs(engine) nodejs010-npm(delegates) nodejs010-npm(readable-stream)* – >> THIS IS FROM CBS mock log

and following is my build log:-
*Requires: nodejs010-nodejs(engine) nodejs010-npm(delegates) >= 0.1.0
nodejs010-npm(delegates) < 0.2 nodejs010-npm(readable-stream) >1.1.13 nodejs010-npm(readable-stream) < 2* I am not sure, why parsing of these version is defining a range, maybe its coming from package.json file. I feel, its related to nodejs010-build package which has root/usr/lib/rpm/nodejs010.req, i defined mock configuration like this:- config_opts[‘root’] = ‘epel-7-x86_64’ config_opts[‘target_arch’] = ‘x86_64’ config_opts[‘legal_host_arches’] = (‘x86_64’,) config_opts[‘chroot_setup_cmd’] = ‘install @buildsys-build scl-utils-build nodejs010-build’ Do they look good? Following is my build.log [sbhutani@localhost ~]$ cat nodejs-build/nodejs010- Display all 316 possibilities? (y or n) [sbhutani@localhost ~]$ cat nodejs-build/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.src.rpm/build.log Mock Version: 1.2.18 ENTER [‘do’]([‘bash’, ‘–login’, ‘-c’, ‘/usr/bin/rpmbuild -bs –target x86_64 –nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec’], chrootPath=’/var/lib/mock/epel-7-x86_64/root’shell

LEAVE A COMMENT