Bug 15144 - php-ZendFramework new bugfix release 1.2.11 available
Summary: php-ZendFramework new bugfix release 1.2.11 available
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Spuhler
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-27 17:12 CET by David Walser
Modified: 2015-03-02 23:19 CET (History)
0 users

See Also:
Source RPM: php-ZendFramework-1.12.9-1.mga5.src.rpm
CVE:
Status comment:


Attachments

Description David Walser 2015-01-27 17:12:33 CET
Upstream has released a new bugfix version on January 14:
http://framework.zend.com/blog/zend-framework-1-12-10-released.html

It's probably worth updating in Cauldron at least, for the bugfixes.

For Mageia 4, I'm sure there will be another security release at some point, so we can wait for that.

Speaking of which, ZF2015-01 only affects php-ZendFramework2.  I've assigned Bug 15143 to guillomovitch for that.

Reproducible: 

Steps to Reproduce:
Comment 1 Thomas Spuhler 2015-01-27 17:33:34 CET
sounds good to me

Status: NEW => ASSIGNED

Comment 2 Thomas Spuhler 2015-01-27 23:47:11 CET
It also has some regressions:
no demos
fonts have been dropped too.

I am going to wait a few days to see what Fedora does.
Comment 3 David Walser 2015-01-27 23:54:18 CET
That sounds like a good idea.  Thanks Thomas.
Comment 4 David Walser 2015-03-02 02:25:26 CET
Upstream has released version 1.2.11 on February 11:
http://framework.zend.com/blog/zend-framework-1-12-11-released.html

Fedora actually did update it this time.

Summary: php-ZendFramework new bugfix release 1.2.10 available => php-ZendFramework new bugfix release 1.2.11 available

Comment 5 Thomas Spuhler 2015-03-02 19:03:48 CET
Cauldron, committed in svn.
Asked for Freeze Push
Comment 6 David Walser 2015-03-02 23:19:01 CET
php-ZendFramework-1.12.11-1.mga5 uploaded for Cauldron.

Thanks Thomas.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.