On 10/11/2014 04:13 PM, Sam Kottler wrote:
I’m the primary maintainer in EPEL + Fedora. Would certainly be able to help
on the CentOS side as well and apply patches as needed.
While some of the patches have different names, it looks like we
(CentOS) have 4 patches that are not included
On Friday, September 12, 2014 at 1:01 PM, Kevin Fenzi wrote:
On Thu, 11 Sep 2014 09:27:32 +0100
Karanbir Singh mail-li...@karan.org (mailto:mail-li...@karan.org) wrote:
that would work. There is the whole fundamental issue to then work
through as to how far the epel branch's can diverge
On Tue, 09 Sep 2014 19:07:57 +0100
Karanbir Singh mail-li...@karan.org wrote:
On 09/09/2014 04:50 PM, Jim Perrin wrote:
Alternatively, is cloud-init an actual shipped RH package that
should be excluded/blacklisted from epel?
its certainly used in the RHEL image
Odd. I am not seeing
hi guys,
The cloud-init is causing lots of issues and we need to workout how best
to handle this.
We have a cloud-init in the CentOS Instance SIG that is curated locally,
based off the last EL7 cloud-init ( 0.7.5 ); but there is now a
cloud-init in epel7 as well, which has a different patchset
On 09/09/2014 10:02 AM, Karanbir Singh wrote:
hi guys,
The cloud-init is causing lots of issues and we need to workout how best
to handle this.
We have a cloud-init in the CentOS Instance SIG that is curated locally,
based off the last EL7 cloud-init ( 0.7.5 ); but there is now a
On 09/09/2014 04:50 PM, Jim Perrin wrote:
Alternatively, is cloud-init an actual shipped RH package that should be
excluded/blacklisted from epel?
its certainly used in the RHEL image
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key :
