Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Yum update issue

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Yum update issue


Chronological Thread 
    < Chronological >      < Thread >
  • From: Tao Zhang <>
  • To: Mark Feit <>, "" <>
  • Subject: Re: [perfsonar-user] Yum update issue
  • Date: Fri, 19 Jun 2020 15:10:09 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=canarie.ca; dmarc=pass action=none header.from=canarie.ca; dkim=pass header.d=canarie.ca; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WqaYw9UZ0jfo76yX/ajvXrQ9Qlt4o65fxvm6b17q9Yw=; b=U2BNgPu5V5NFHUgffW331BV/p8+x0SV9HANQtoMnDZkaewQWRL/99ylXX0DN8ZDUwXrboOsCuWgVsbsjQ2ONbT2H76IO7TURaK4M7h/MTs5lwRywn+K9xHQfjLz01a9peCnQqa+/igsGE+nmfxU3lcTUYwOmqyF/4KmQ7nlHt6F2n72jB4/KYylww6EfBhweoAgEJfJNZ6P/0EmAH/lyeDf5Csl5MlJ1KLs0UkNmUw3Mgkd/BTaMD+Hq74cc7Q6dHiPQ6NLYaJpq/qtqqmfxlNMg8IZCOJHsGE5WH3cVTDfXyg6/BcinJFei+tpG4hdNb3LRdEp/NlEs0Kcy8wH9tQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=WtYKLqaHUZAzkjYLpDkyi5HrDtrO7xWI7CbyUJEQx+OQPnGsBhQsXCgEEV9PScWaZG+IJg0I2nfP5fzCHUzxVYZL39sSM3FdM7RNvttd02bwZzMS4RkMjiksv3pcf/FEOORCHoZZGsOmJ/nm9XhtgGaAwuIBMGSrQKGUJ7IiVYiZHm0V+PUa2MVWjygoQbKdnqMJl3VEa7zKm468vMjc6UluZRWTqiEs0EqEJJR5cYXA/rXbOijD7xCfHNiZ5ZSDAA0MwLk5k0aLkoRniViGX9onwbYPg5zHKPO0qwec1jN9DSTi1I6FhVvQBPLezetDSrkhrvery0uWrvaewzx6YQ==
Thank you Mark for the quick fix.

Have a good and safe weekend!

Tao

From: Mark Feit <>
Sent: Friday, June 19, 2020 11:08 AM
To: Tao Zhang <>; <>
Subject: Re: [perfsonar-user] Yum update issue
 

I wrote:

 

Tao Zhang writes:

 

Got an issue with yum update on the perfsonar box, looks like something wrong with the package  jq-1.6.10-1.el7.x86_64

 

I’ll have a look at that.  Every so often, a CentOS upgrade breaks something in perfSONAR; this may be one of them.

 

This was indeed one of those cases:  EPEL upgraded the dependency to a version with a slightly different API, which was enough to break the jq package’s dependency.

 

We have a fix and will release it Monday.

 

--Mark

 


Archive powered by MHonArc 2.6.19.

Top of Page