pecl rebuilds

[Brandon Holbrook <fedora@xxxxxxxxxxxxxxxx>]

All,

After just upgrading one of my development boxes to f7, I started 
getting a lot of PHP warnings when the PHP engine starts similar to the 
following:

PHP Warning:  PHP Startup: apc: Unable to initialize module
Module compiled with module API=20050922, debug=0, thread-safety=0
PHP    compiled with module API=20060613, debug=0, thread-safety=0

and

PHP Warning:  PHP Startup: mailparse: Unable to initialize module
Module compiled with module API=20050922, debug=0, thread-safety=0
PHP    compiled with module API=20060613, debug=0, thread-safety=0

(apc has already been bugzilla'd at 
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=244045)

apc and mailparse are the only 2 complaining on my box, and a quick "yum 
list *pecl*" verifies both of these modules still bear a 'fc6' disttag.  
Needless to say, since pecl modules are compiled against a specific PHP 
version, this is unacceptable.  In addition to rebuilding these packages 
for f7 asap, I'd like to come up with a good policy about making 
mandatory rebuilds of pecl packages whenever the PHP core ABI gets 
updated.  Is it reasonable to assume ABI updates only happen between 
fedora releases, or do we need to also address planning simultaneous php 
and php-pecl-* updates mid-release?  Other thoughts?

-Brandon

_______________________________________________
Fedora-php-devel-list mailing list
Fedora-php-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-php-devel-list