Re: [Rdo-list] Why use yum priority in rdo-release repo file?
On 06/20/2013 12:03 PM, Pádraig Brady wrote:
On 06/20/2013 09:30 AM, Sandro "red" Mathys wrote:
> Even though RDO is supposed to always being ahead of RHEL and EPEL, it enforces a
higher priority (lower priority=N) than the default. Why?
So yes this is debatable.
y-p-p is used with the RHOS product to give precedence over EPEL.
I.E. even though EPEL is not required there, con existence is supported.
Now RDO requires EPEL so again y-p-p gives us the flexibility for RDO to override EPEL.
Now whether this is actually required at present is not obvious.
We could retain the flexiblity while avoiding problems with y-p-p
by keeping the overlapping set as small as possible.
wrt puppet, I'm not sure why it's there TBH.
EPEL has 2.6.18-3 while puppet-2.6.18-2 is in the RDO repo.
I've asked around a little and will probably just remove
puppet from the RDO repo, which will fix your immediate problem.
So I found the reason that puppet was in RDO from the following commit.
It was a temp workaround I made in the rush to get a working RDO out the door,
and completely forgot about. Now the update in epel should fix this issue,
so the plan above to remove puppet from RDO should work, and I've now done that.
thanks,
Pádraig.
commit 18a8667ad0ce3046b5a83edfb3df2f85c1ba2c3d
Author: Pádraig Brady <P(a)draigBrady.com>
Date: Tue Apr 9 16:34:17 2013 +0100
bump release to supersede problematic EPEL package
Avoid https://bugzilla.redhat.com/show_bug.cgi?id=949549
diff --git a/puppet.spec b/puppet.spec
index f7eb4cc..8468e7b 100644
--- a/puppet.spec
+++ b/puppet.spec
@@ -13,7 +13,7 @@
Name: puppet
Version: 2.6.18
-Release: 1%{?dist}
+Release: 2.1%{?dist}
Summary: A network tool for managing many disparate systems
License: GPLv2
URL: http://puppetlabs.com
@@ -290,7 +290,7 @@ fi
rm -rf %{buildroot}
%changelog
-* Mon Mar 11 2013 Michael Stahnke <stahnma(a)puppetlabs.com> - 2.6.18-1
+* Mon Mar 11 2013 Michael Stahnke <stahnma(a)puppetlabs.com> - 2.6.18-2.1