Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] postgresql9.5 dependency in perfsonar & obsolete packages

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] postgresql9.5 dependency in perfsonar & obsolete packages


Chronological Thread 
  • From: Mark Feit <>
  • To: Gerald Vogt <>, "" <>
  • Subject: Re: [perfsonar-user] postgresql9.5 dependency in perfsonar & obsolete packages
  • Date: Fri, 7 May 2021 15:49:26 +0000

Gerald Vogt writes:


… I cannot remove the old perfsonar95 rpms because of dependencies:

---> Package postgresql95-server.x86_64 0:9.5.3-2PGDG.rhel7 will be erased
postgresql-load-1.1-1.el7.noarch
pscheduler-server-4.3.4-1.el7.noarch

So basically it removes the whole pscheduler-server and perfsonar
because of the dependencies to postgresql-load.noarch which depends on
postgresql95. I guess, postgresql-load.noarch should not depend on a
specific postgresql server version?

 

The version of postgresql-load you have installed depends only on PostgreSQL 10, so that shouldn’t be the cause.  The naming of the packages specifically as posrgresql95-* is a quirk of how it was packaged by PGDG and Red Hat.  I’d be interested to see what “rpm -q whatrequires postgresql95-server” yields.  There shouldn’t be anything left on the system that requires it.


I also checked with "yum autoremove" and it lists a number of obsolete
packages:

  perl-Net-Netmask         noarch   1.9015-13.el7 @epel7-centos7-x86_

 

There was a historical requirement for that package that no longer exists.


  postgresql95-contrib     x86_64   9.5.3-2PGDG.rhel7 @perfSONAR
  postgresql95-devel       x86_64   9.5.3-2PGDG.rhel7 @perfSONAR
  postgresql95-plpython    x86_64   9.5.3-2PGDG.rhel7 @perfSONAR

 

Those were dependencies prior to 4.3.  As mentioned above, all of postgresql95 should go with it.


  python-daemon            noarch   1.6-4.el7 @epel7-centos7-x86_64
  …
Are those really obsolete or are they not listed properly in other rpms
depending on them?

 

All of the python-* packages are holdovers from Python 2, which we no longer use.  Red Hat went through the same naming weirdness with the Python 2-to-3 transition that it did during the 32-to-64-bit transition.  Basically, anything that’s python-* or python2-* is Python 2 and anything that’s Python3*-* is Python 3.  The extra wildcard in the Python3 stuff has to do with inconsistency in the way Red Hat named packages between EL7 and EPEL.

 

Some of the systems in our test bed get rebuilt from scratch regularly, so missing dependencies would stand out like a sore thumb.

 

--Mark

 

 




Archive powered by MHonArc 2.6.24.

Top of Page