Re: [Fwd: Pear broken in php 5.2.11]

On Wed, Oct 28, 2009 at 11:28 AM, till <klimpong@gmail.com> wrote: > Hey guys, > > can anyone enlighten me how the release process of PEAR in a phar works? If php is compiled from svn, the latest phar is pulled in from the pear website. PHP releases are distributed with the phar that was available at the time of tagging/packaging. The phar files can be built by checking out pear-core and running the related make-* build scripts. Once we have a new phar to release, we package up a PEAR package that contains the phars. http://pear.php.net/package/pearweb_phars That pearweb_phars-x.x.x.tgz file is uploaded through the standard developer upload release form. Once that happens, the server running pearweb is supposed to automatically upgrade the installed version on the server, which places the new phars on the pear website. What Helgi and I discovered was that the upgrade cron job on the server was not running, which prevented the new phar file from being available at http://pear.php.net/install-pear-nozlib.phar at the time 5.2.11 was packaged, ergo, 5.2.11 was tagged and released with the same broken 5.2.10 phar. The latest phar is available through the web now, and I believe this phar works fine. -- Brett Bieber