perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

Marian Babik writes:

 

it’s from this release:

http://mirror.in2p3.fr/pub/linux/internet2-software/rpms/el7/x86_64/4.3.0/RPMS/

 

RPM is still in the repo.

 

These are the packages in the repo for 4.2.0 and later and their dependencies:

 

4.2.0/packages/jq-1.6-1.el7.x86_64.rpm                libonig.so.2         EPEL was still supplying 1.5

4.2.1/packages/jq-1.6-1.el7.x86_64.rpm                libonig.so.2

4.2.3/packages/jq-1.6-1.el7.x86_64.rpm                libonig.so.2

4.2.3/packages/jq-1.6.10-1.el7.x86_64.rpm          libonig.so.2         EPEL starts shipping 1.6, added minor number to dodge it

4.2.4/packages/jq-1.6.10-1.el7.x86_64.rpm          libonig.so.2

4.2.4/packages/jq-1.6.10-2.el7.x86_64.rpm          libonig.so.5         New version of Oniguruma in EPEL

4.3.0/packages/jq-1.6.10-1.el7.x86_64.rpm          libonig.so.5

4.3.0/packages/jq-1.6.10-2.el7.x86_64.rpm          libonig.so.5         Not sure why we have a -1 and a -2 in 4.3.0, too.

4.3.2/packages/jq-1.6.10-1.el7.x86_64.rpm          libonig.so.5         4.3.1 was one package slipped in atop 4.3.0, hence the gap

4.3.3/packages/jq-1.6.10-1.el7.x86_64.rpm          libonig.so.5

4.3.4/packages/jq-1.6.10-1.el7.x86_64.rpm          libonig.so.5

4.4.0/packages/jq-1.6.10-1.el7.x86_64.rpm          libonig.so.5

4.4.1/packages/jq-1.6.10-1.el7.x86_64.rpm          libonig.so.5

 

We have, on occasion, slipped revisions to single packages into the repository instead of doing a full build and release, and this might be one of those cases.  It looks like whatever change there was to cause -2 to happen (would have been an RPM spec or patch change only) never made it back into version control and subsequent packages went back to being -1.  And it seems to have happened twice.  At some point, I’m going to have to dissect the SRPMs and see what we did.  At any rate, the only -1 package that depended on liboning.so.2 should have been upgraded to a -2 at some point.

 

For me all works fine and I also have this RPM on another box, so likely there are many out there with the same package/release. I guess the question to answer is: what’s the correct requirement on libonig in jq ?

 

For me it’s:

# rpm -q --requires jq-1.6.10-2.el7.x86_64 | grep libo

libonig.so.5()(64bit)

 

We take whatever version of Oniguruma is in EPEL at the time of build.  In the current EPEL-supplied version, that’s libonig.so.5.  The -2 packages depend on that.  The only explanation I can come up with for what Jean-Michel is seeing is that the system being upgraded is 4.2.3 or earlier or 4.2.4 with jq-1.6.10-1.  There’s a 4.4.2 in the pipeline with some minor changes; I’ve bumped jq to 1.6.10-3 so packages on older systems are forced into the right state when that upgrade occurs.

 

--Mark