Your message dated Sun, 16 Aug 2015 14:07:37 +0200
with message-id <[email protected]>
and subject line Re: Packaging some ZendFramework components
has caused the Debian Bug report #721262,
regarding Please package Zend Framework 2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
721262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721262
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: zendframework
Version: 1.12.3-1
There's a new upstream version (2.2.2) available, which should be packaged.
--- End Message ---
--- Begin Message ---
Hi,
Le 07/08/2014 01:03, David Prévot a écrit :
> I’m not up to the task of packaging the whole zendframework version 2
> right now (but if someone is, please just claim #721262), but I’m
> willing to package the zend-code component (e.g., as php-zend-code).
Upstream already split the ZendFramework packages, some are already in
Debian: php-zend-code, php-zend-db, php-zend-eventmanager,
php-zend-search, php-zend-stdlib, and php-zend-xml (but that last one is
going away).
If some components are needed, I guess the usual ITP/RFP process should
do, and the zendframework version 1 package will probably die before
Stretch gets released. If relevant, we can make zendframework a
metapackage depending on the php-zend-* components, but we’re far from
having enough php-zend-* components right now to provide something
feature equivalent.
Regards
David
signature.asc
Description: OpenPGP digital signature
--- End Message ---
