perfSONAR User Q&A and Other Discussion

[Marian Babik <>]

Hi Mark,

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

I would guess that jq release 1 package still has libonig.so.2 ? 

Thanks,

Marian

On Sep 8, 2021, at 5:50 PM, Mark Feit <> wrote:

Jean-Michel Barbet writes:

Your jq from Perfsonar has a minor release -2 while mine is -1 :

[root@nanperfs01 ~]# rpm -qa | grep jq-1
jq-1.6.10-1.el7.x86_64

 

I checked every version of the jq spec in our repository (see https://github.com/perfsonar/pscheduler/commits/master/jq/jq.spec) and can’t find any instance where we shipped with a -2 release.  So I’m a little puzzled about where Marian’s jq-1.6.10-2 came from.  It clearly wasn’t EPEL; they’re at 1.6-2, and that shouldn’t be installed.

 

The path of least resistance here might be to either rebuild the system or, if that’s impractical, erase oniguruma, jq and pscheduler-* and then reinstall whichever bundle was initially installed.

 

Some days, I find myself wondering of the folks who Dockerize everything may be onto something.  :-)

 

--Mark

 

--
To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user

Attachment: smime.p7s
Description: S/MIME cryptographic signature