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 > cloud-init in epel7 as well, which has a different patchset but higher > Release id. > > I could now go and build a higher Release, but can we workout a better > longer term solution to stuff like this ?
As the patches used in the CentOS package have been accepted upstream, perhaps they could be merged into the epel package so that there's only one shipped. Alternatively, is cloud-init an actual shipped RH package that should be excluded/blacklisted from epel? -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77 _______________________________________________ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel