Hi,
On 2015-03-09 17:41, Dave Brolley wrote:
> On 03/09/2015 04:56 AM, Ken McDonell wrote:
>> On 09/03/15 19:09, Marko Myllynen wrote:
>>>
>>> on few remaining RHEL 5 systems I'm seeing this update issue:
>>>
>>> root@localhost:~# yum update --enablerepo=epel-testing
>>> Loaded plugins: downloadonly, priorities, rhnplugin, security,
>>> versionlock
>>> This system is receiving updates from RHN Classic or RHN Satellite.
>>> Skipping security plugin, no data
>>> Reading version lock configuration
>>> Setting up Update Process
>>> Resolving Dependencies
>>> Skipping security plugin, no data
>>> --> Running transaction check
>>> ---> Package pcp.i386 0:3.10.3-1.el5 set to be updated
>>> --> Processing Dependency: perl(JSON) for package: pcp
>>> ...
>>> --> Finished Dependency Resolution
>>> python-pcp-3.9.5-1.el5.i386 from installed has depsolving problems
>>
>> Don't know why there is no python-pcp-3.10.3 in the epel-tesing repo
>> ... checked with
>> https://dl.fedoraproject.org/pub/epel/testing/5/x86_64/ and it ain't
>> there.
>>
>> Can someone from RH who understands the process for source on
>> oss.sgi.com -> rpms in epel-testing care to explain?
> According to the spec file, python-pcp is disabled in epel5. The comment
> says that the python version there (pre-2.6) is too old. So no
> python-pcp-3.10.3-1 was built.
in that case you need to Obsolete the python-pcp package in another
package so that you won't break system updates for those who have it
installed.
Thanks,
--
Marko Myllynen
|