php-pear package problems (Karmic)

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

Pear + Pecl Channel issue:
---------------------------------------

Steps to reproduce:

1) sudo apt-get install php-pear
2) sudo pear install {any package}

result:
pear.php.net is using a unsupported protocal - This should never happen.
install failed

Work around:

1) sudo rm -R /usr/share/php/.channels
2) sudo pear update-channels

---------------------------------------
Broken Symlink issue:
---------------------------------------

Steps to reproduce:

1) cd /usr/share/php/
2) ls -al

Result:
Symlink Doc is broken

Work around:
1) sudo rm /usr/share/php/doc
2) sudo ln -s /usr/share/doc/php-pear /usr/share/php/doc

I'm not sure how the .deb was packaged, but I suspect using a newer phar from the PEAR website, or the phar packaged with PHP-5.2.11 should fix this.
http://pear.php.net/install-pear-nozlib.phar

This bug is technically two bugs in one.

1) A borked symlink (which is also present in upstream)

2) A borked phar in the 5.2.10 release.

OK I can reproduce the dangling symlink. This is really 2 bug reports in one. Can you seperate out the two bugs here?

Thanks
chuck

I'd say "yes", but I don't know what it entails. :-)

Troubleshooting of the bad phar file issue has been done from the PEAR side on PEAR bug #16606 [1], in case that info helps with decisions on how to resolve the php-pear packaging in Karmic.

[1] -- http://pear.php.net/bugs/bug.php?id=16606

I was able to reproduce this:

Setting up php-pear (5.2.10.dfsg.1-2ubuntu4) ...
chuck@kenny:~/work/server/samba/samba-3.4.1$ sudo pear -vv install Net_FTP
pear.php.net is using a unsupported protocal - This should never happen.
Cannot initialize 'channel://pear.php.net/Net_FTP', invalid or missing package file
Package "channel://pear.php.net/Net_FTP" is not valid
install failed

I might have a fix for this bug.

Thanks
chuck

Ok there are actually two bugs here. I will concentrate on the pear bug hear please open another bug for the dangling symlink its less important right now.

So here are the things I have tried to fix this bug:

- Applied the patch from the php bug. (Still the same result)
- Patching the phar file (wont work checksums mismatch)
- Replacing the phar file (wont work build will fail)

So Im look for feedback on how to fix this bug short of merging php 5.2.11 from debian.

Regards
chuck

Given that the bad PEAR phar was packaged with both the 5.2.10 and 5.2.11 releases of PHP, the "fix" should definitely be creating your working PEAR installation by using the current working phar file from [1] rather than from one that was included with those two PHP releases. Judging from the file list I see for the karmic package [2], I'm not sure I can guess why you are experiencing "wont work build will fail". Don't you build the karmic package using the files from a successful PEAR installation?

[1] -- http://pear.php.net/install-pear-nozlib.phar
[2] -- http://packages.ubuntu.com/karmic/all/php-pear/filelist

This bug was fixed in the package php5 - 5.2.10.dfsg.1-2ubuntu5

---------------
php5 (5.2.10.dfsg.1-2ubuntu5) karmic; urgency=low

  * debian/control, debian/patches/115-autoconf_ftbfs.patch:, debian/series:
    Drop patch build-depend on autoconf2.13
  * pear/install-pear-nozlib.phar: PHP 5.2.10 was shipped with a broken
    install-pear-nozllib.phar which caused pear to be broken. Use the
    version from http://pear.php.net. (LP: #420639)
  * debian/patches/fix-zlib-decompression: Add upstream fix from 5.2.11
    fo fix zlibe.deflage compress filter to actually accept level parameter.
  * debian/rules: Fix symlink for pear.

 -- Chuck Short <email address hidden> Tue, 13 Oct 2009 10:56:29 -0400

The symlink and zlib issues seem to remain in 5.2.10.dfsg.1-2ubuntu5 per our testing on #pear... new bugs for each are forthcoming...

Symlink bug -- #451277

zlib bug -- #451314