-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/04/2013 06:14 AM, Michael Schwendt wrote:
On Wed, 3 Apr 2013 16:54:03 -0500, Richard Shaw wrote:
> On Wed, Apr 3, 2013 at 3:56 PM, Adam Williamson wrote:
>
>> Note that we're frozen for Alpha, so this won't go in stable
>> until after Alpha release unless there's a legitimate reason to
>> make it a freeze exception issue -
>>
https://fedoraproject.org/**
>>
wiki/QA:SOP_freeze_exception_**bug_process<https://fedoraproject.org/w...;.
>>
>
>
>>
Nah... I've waited this long. At least a fix is coming.
It would have been possible for you to work around the missing
#include by adding it to the source code you wanted to build. Never
has there been a requirement to "wait for alsa-lib".
Sure, but my interpretation of the problem is that this was causing
FTBFS on any package in F19 that was trying to BuildRequires:
alsa-lib-devel because of changes made in GCC. It seems like the
correct behavior for alsa-lib to restore the existing functionality
than to force all downstreams to include a hack around the problem.
And it was nice and easy.
But yes, I certainly follow your point about his particular package
having the *option* of hacking around it if there was an urgent need.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -
http://www.enigmail.net/
iEYEARECAAYFAlFdcV8ACgkQeiVVYja6o6PBvACbBZaRDFkyHnXWm7TGNGOYmxEF
6KEAoIWTcp5SFbzyfT8ILhCKTFPWwtxZ
=sogc
-----END PGP SIGNATURE-----