[Pacemaker] corosync rpm from cluster.org/rpm repo

[Andrew Beekhof]

On Thu, Dec 9, 2010 at 5:50 PM, Larry Brigman <larry.brigman at gmail.com> wrote:
> On Thu, Dec 9, 2010 at 1:57 AM, Andrew Beekhof <andrew at beekhof.net> wrote:
>> On Wed, Dec 8, 2010 at 10:36 PM, Larry Brigman <larry.brigman at gmail.com> wrote:
>>> Why is there no 1.2.8 corosync rpm in any of the
>>> http://www.clusterlabs.org/rpm repo directories?
>>>
>>> It says that the latest version of pacemaker was tested that version here:
>>> http://www.clusterlabs.org/wiki/Install#Versions_and_Compatibilty
>>>
>>> Was there no public rpm version built?
>>
>> Good point.  I used 1.2.8 from the fedora 13 update repo.
>> The packages on http://www.clusterlabs.org/rpm are built against the
>> latest version from either the distro or our repo.
>>
>> So if the repo has 1.2.7 but the distro has been updated to 1.2.8,
>> then 1.2.8 will be used form the distro.
>> This is why it is important to use the .repo file (eg.
>> http://www.clusterlabs.org/rpm/fedora-13/clusterlabs.repo) rather than
>> downloading things manually.
>>
>> On a related note, the clusterlabs repos will eventually probably only
>> contain pacemaker at some point.
>> This is because our dependancies are all pretty rock solid these days
>> and just about every distro ships a version that is recent enough.
>>
>> Does that help?
> Not really because...
> I use a repo file for the cluster labs repo but the updated package is
> not there.
> I would use the EPEL repo but corosync isn't in the repo.
> I'm using RHEL5.5

In the case of EPEL5, Pacemaker was built against 1.2.7 which is in
the clusterlabs repo.
Is there a specific problem that requires you to have 1.2.8?

As I explained above, anything even remotely recent from corosync (or
the other projects) is usually sufficient, this includes corosync
1.2.7.
I'm not aiming to replace the entire distribution, if you need higher
frequency updates perhaps its something you should bring up with the
EPEL maintainers.