<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Dec 26, 2013 at 6:12 PM, Kevin Fenzi <span dir="ltr"><<a href="mailto:kevin@scrye.com" target="_blank">kevin@scrye.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="im">On Thu, 26 Dec 2013 16:53:19 -0800<br>
Michael Stahnke <<a href="mailto:stahnma@puppetlabs.com">stahnma@puppetlabs.com</a>> wrote:<br>
<br>
> What's the process opt-in at this point? I'm a bit unclear. I see that<br>
> epel-release was built for EPEL7 (and that the git branch is epel7<br>
> instead of el7).<br>
<br>
</div>There's no process yet because we don't have some things we still need<br>
done yet. ;)<br>
<br>
Dennis is working on getting fedup and mock and such in place. Once<br>
those are working we should be able to get a good compose (it's<br>
currently enabled, but just failing every night due to missing items).<br>
<br>
I expect things will start moving along after the holidays and as soon<br>
as things are ready for more packages we will announce. ;)<br></blockquote><div><br><a href="http://www.karan.org/blog/2014/01/02/an-epel-build-in-rhel7b1/">http://www.karan.org/blog/2014/01/02/an-epel-build-in-rhel7b1/</a><br>
</div><div>That isn't anything official, but it let me see that my EPEL packages built just fine on EL7 beta and is probably a decent indicator of potential problems in a general sense.<br></div></div></div></div>