pcp
[Top] [All Lists]

Re: [pcp] PCP / RHEL 5 Update Issue

To: myllynen@xxxxxxxxxx, Ken McDonell <kenj@xxxxxxxxxxxxxxxx>, Dave Brolley <brolley@xxxxxxxxxx>
Subject: Re: [pcp] PCP / RHEL 5 Update Issue
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Mon, 9 Mar 2015 18:58:27 -0400 (EDT)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <54FDD019.5030202@xxxxxxxxxx>
References: <54FD554B.3020403@xxxxxxxxxx> <54FD6039.3060600@xxxxxxxxxxxxxxxx> <54FDBF32.7040104@xxxxxxxxxx> <54FDD019.5030202@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: yS/qTRxVGu0zCbkMSwDewZVozoOMIQ==
Thread-topic: PCP / RHEL 5 Update Issue
Hi guys,

----- Original Message -----
> [...]
> >> 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.

*nod*

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

It turns out there's a python26 in EPEL5 - I'll look into switching the
epel5 builds to using that for the next release such that we get back
the python monitoring tools, PMDAs and APIs there.

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>