<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Feb 27, 2015 at 8:50 AM, Peter Robinson <span dir="ltr"><<a href="mailto:pbrobinson@gmail.com" target="_blank">pbrobinson@gmail.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"><span class="">On Fri, Feb 27, 2015 at 3:23 PM, Dave Johansen <<a href="mailto:davejohansen@gmail.com">davejohansen@gmail.com</a>> wrote:<br>
> On Tue, Feb 24, 2015 at 11:24 AM, Dennis Gilmore <<a href="mailto:dennis@ausil.us">dennis@ausil.us</a>> wrote:<br>
>><br>
>> Today is also the Alpha freeze[4]. This means that only packages which<br>
>> fix accepted blocker or freeze exception bugs[5][6] will be marked as<br>
>> 'stable' and included in the Alpha composes. Other builds will remain<br>
>> in updates-testing until the Alpha release is approved, at which point<br>
>> the Alpha freeze is lifted and packages can move to 'stable' as usual<br>
>> until the Beta freeze.<br>
><br>
><br>
> I have a question on how I'm supposed to handle a new package. I was working<br>
> on packaging iwyu [1] and it built for all of the target releases except for<br>
> F22 because of some gcc 5.0 issues. It appears that the last one has been<br>
> resolved [2], so how do I handle this situation? Do I just wait until the<br>
> alpha freeze is over to build iwyu for F22? Or should I use a buildroot<br>
> override?<br>
<br>
</span>Build it as per normal, if it's a single package submit it to bodhi as<br>
an update for F-22, if you need to build other packages against it<br>
you'll need to do a build override as per normal stable releases.</blockquote><div><br><a href="http://koji.fedoraproject.org/koji/taskinfo?taskID=9096041">http://koji.fedoraproject.org/koji/taskinfo?taskID=9096041</a><br></div><div>The package doesn't build and needs the gcc update in order to build. <br></div></div></div></div>