Sounds good! Thanks for the good work.<div><br></div><div>Regards,</div><div>Andreas<span></span><br><br>Am Montag, 22. Juli 2013 schrieb Michael Cronenworth :<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 07/21/2013 09:12 AM, Erik van Pienbroek wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In the last couple of days I've been working with upstream mingw-w64<br>
developers to resolve all known build failures (with exception of the<br>
ones which are caused by winpthreads). We're currently at a point where<br>
we feel confident with the current state. I plan on doing one more test<br>
mass rebuild (without winpthreads) to make sure all build failures are<br>
resolved now.<br>
<br>
Here's what I would like to propose:<br>
<br>
1. Update mingw-w64 in rawhide and f19-updates-testing to<br>
today's snapshot<br>
2. Kick off a test mass rebuild without winpthreads to make<br>
sure there are no more build failures<br>
3. Once we've got a confirmation that all build failures are<br>
really resolved, push these updated mingw-w64 packages to<br>
f18-updates (with buildroot overrides in place for the time<br>
the packages have to spend in updates-testing)<br>
4. Afterwards the wine maintainer can build and push updated<br>
versions of mingw-wine-gecko and wine itself to f18<br>
<br>
Does this sound like a good plan to you folks?<br>
</blockquote>
<br>
<br>
Sounds fine to me.<br>
<br>
CC'ing wine/gecko maintainer.<br>
<br>
</blockquote></div><br><br>-- <br><div dir="ltr">BR Andreas Bierfert, M.Sc. | phone: +49 33056 423336 | GPG: C58CF1CB<br><a href="mailto:andreas.bierfert@lowlatency.de" target="_blank">andreas.bierfert@lowlatency.de</a> | fax: +49 33056 423338 | signed/encrypted<br>
<a href="http://lowlatency.de" target="_blank">http://lowlatency.de</a> | cell: +49 170 9665206 | mail preferred</div><br>