PEAR Bug Search Results

PEAR: Bug 16767 [Open] Use of Depreciated HTML Attributes

fuhrysteve at gmail dot com — 2009-11-05T19:50:30+00:00

PEAR Bug
Reported by fuhrysteve
2009-11-05T19:50:30+00:00
PHP: Irrelevant OS: any Package Version: 1.9.0

Description:
------------
Depreciated HTML attributes such as:
bgcolor="#aaaaaa"

should be:
style="background:#aaaaaa"

for forward compatibility

PEAR: Bug 16654 [Open] "pear upgrade-all" fails with Warning: mkdir(): File exists

mjs at beebo dot org — 2009-09-28T23:06:03+00:00

PEAR Bug
Reported by mjs
2009-09-28T23:06:03+00:00
PHP: 5.3.0 OS: Ubuntu Package Version: 1.9.0

Description:
------------
Output of "pear upgrade-all":

mel:~$ pear upgrade-all
Will upgrade channel://pear.php.net/pear
downloading PEAR-1.9.0.tgz ...
Starting to download PEAR-1.9.0.tgz (291,634 bytes)
.............................................................done: 291,634 bytes

Warning: mkdir(): File exists in System.php on line 277
PHP Warning:  mkdir(): File exists in /usr/local/php-
5.3.0/lib/php/System.php on line 277
PHP Stack trace:
PHP   1. {main}() /usr/local/php-5.3.0/lib/php/pearcmd.php:0
PHP   2. PEAR_Command_Common->run() /usr/local/php-
5.3.0/lib/php/pearcmd.php:308
PHP   3. PEAR_Command_Install->doUpgradeAll() /usr/local/php-
5.3.0/lib/php/PEAR/Command/Common.php:271
PHP   4. PEAR_Command_Install->doInstall() /usr/local/php-
5.3.0/lib/php/PEAR/Command/Install.php:902
PHP   5. PEAR_Installer->install() /usr/local/php-
5.3.0/lib/php/PEAR/Command/Install.php:710
PHP   6. PEAR_Installer->_installFile2() /usr/local/php-
5.3.0/lib/php/PEAR/Installer.php:1411
PHP   7. PEAR_Installer->mkDirHier() /usr/local/php-
5.3.0/lib/php/PEAR/Installer.php:547
PHP   8. PEAR_Common->mkDirHier() /usr/local/php-
5.3.0/lib/php/PEAR/Installer.php:997
PHP   9. System->mkDir() /usr/local/php-
5.3.0/lib/php/PEAR/Common.php:234
PHP  10. mkdir() /usr/local/php-5.3.0/lib/php/System.php:277

Warning: mkdir(): File exists in /usr/local/php-5.3.0/lib/php/System.php 
on line 277

Call Stack:
    0.0027     491516   1. {main}() /usr/local/php-
5.3.0/lib/php/pearcmd.php:0
    0.0825    2920260   2. PEAR_Command_Common->run() 
/usr/local/php-5.3.0/lib/php/pearcmd.php:308
    0.0825    2920260   3. PEAR_Command_Install->doUpgradeAll() 
/usr/local/php-5.3.0/lib/php/PEAR/Command/Common.php:271
    0.0848    2938180   4. PEAR_Command_Install->doInstall() 
/usr/local/php-5.3.0/lib/php/PEAR/Command/Install.php:902
    2.8906    8338792   5. PEAR_Installer->install() /usr/local/php-
5.3.0/lib/php/PEAR/Command/Install.php:710
    3.2781   10138160   6. PEAR_Installer->_installFile2() /usr/local/php-
5.3.0/lib/php/PEAR/Installer.php:1411
    3.2785   10143592   7. PEAR_Installer->mkDirHier() /usr/local/php-
5.3.0/lib/php/PEAR/Installer.php:547
    3.2786   10144044   8. PEAR_Common->mkDirHier() /usr/local/php-
5.3.0/lib/php/PEAR/Installer.php:997
    3.2786   10144340   9. System->mkDir() /usr/local/php-
5.3.0/lib/php/PEAR/Common.php:234
    3.2787   10145952  10. mkdir() /usr/local/php-
5.3.0/lib/php/System.php:277

ERROR: failed to mkdir /usr/local/php-5.3.0/bin/php


Expected result:
----------------
A successful upgrade.

Actual result:
--------------
An error message.

PEAR: Feature/Change Request 16648 [Open] Use TMPDIR for builds instead of /var/tmp

gm dot outside+pear at gmail dot com — 2009-09-27T13:06:33+00:00

PEAR Feature/Change Request
Reported by galaxy
2009-09-27T13:06:33+00:00
PHP: 5.2.5 OS: Linux Package Version: 1.9.0

Description:
------------
Currently pecl builds packages in the hardcoded /var/tmp/pear-build-USER/PACKAGE-VERSION .  The /var/tmp/pear-build-USER directory is never removed.  The following patch changes the hardcoded /var/tmp/pear-build-USER into a dynamic temporary directory (in $TMPDIR) which is deleted upon the pecl script termination.

PEAR: Bug 16644 [Open] pear returns syntax error when parenthesis are in install path.

bwaters at solutionsbywaters dot com — 2009-09-25T16:04:31+00:00

PEAR Bug
Reported by bwaters
2009-09-25T16:04:31+00:00
PHP: 5.3.0 OS: Vista-64bit Package Version: 1.9.0

Description:
------------
When installed under C:\Program Files (x86)\ pear returns syntax error because the include_path directive is not properly quoted

Test script:
---------------
C:\Program Files(x86)\Zend\ZendServer\bin>pear

Expected result:
----------------
list of commands....

Actual result:
--------------
Alert box form php thrown -
Syntax Error, unexpected '(' in Unknown on Line 14

PEAR: Bug 16596 [Open] parse error in Unknown on line 14

danielc at analysisandsolutions dot com — 2009-09-11T15:44:06+00:00

PEAR Bug
Reported by danielc
2009-09-11T15:44:06+00:00
PHP: 5.3.0 OS: Windows XP Package Version: 1.9.0

Description:
------------
Running any PEAR command, for example "pear info PEAR", a dialog box pops up.  The title bar says "PHP Error" and the message is "parse error in Unknown on line 14".  This has been happening for a while and still exists after upgrading to 1.9.0.

PEAR: Feature/Change Request 16545 [Open] pear should warn about conflicting parameters

cweiske at php dot net — 2009-08-21T23:32:50+00:00

PEAR Feature/Change Request
Reported by cweiske
2009-08-21T23:30:58+00:00
PHP: Irrelevant OS:  Package Version: 1.9.0RC3

Description:
------------
"pear upgrade -ao" conflict with each other. PEAR should warn the user when he does that.

PEAR: Bug 16394 [Open] PEAR Installer should not write to C:\Windows

sb at sebastian-bergmann dot de — 2009-08-02T13:31:31+00:00

PEAR Bug
Reported by sebastian
2009-07-01T09:40:33+00:00
PHP: 5.3.0 OS: Windows Vista Package Version: 1.8.1

Description:
------------
Downloaded and unpacked http://windows.php.net/downloads/releases/php-5.3.0-nts-Win32-VC9-x86.zip

wget http://pear.php.net/go-pear
php go-pear

Expected result:
----------------
Setup works and does not write anything to C:\Windows

Actual result:
--------------
PEAR_Config::writeConfigFile fopen('C:\Windows\pear.ini','w') failed (fopen(C:\Windows\pear.ini): failed to open stream: Permission denied)

PEAR: Feature/Change Request 16243 [Open] Provide http_proxy config variable for each channel

hoareau dot olivier at gmail dot com — 2009-05-21T14:24:28+00:00

PEAR Feature/Change Request
Reported by ohoareau
2009-05-20T15:39:12+00:00
PHP: 5.2.5 OS: Windows Package Version: 1.8.1

Description:
------------
When using PEAR installer inside a company lan you often 
need to use a proxy to download third party channels.
Indeed, when using your own PEAR channel on your local lan, 
you need to use proxy for third party packages (on internet, 
or for pear.php.net packages for example) BUT no proxy for 
your local packages.
Indeed if one of your local package depends on a third party 
package (example : your create a "desktop installation 
package" that depends on all popular php tools package 
available on internet) when you use the command :
$ pear install mychannel/mypackage
the PEAR installer will need to access directly the mychannel 
channel BUT to use a proxy to pick up the packages and 
channel.xml (REST files) on the dependencies channels.

Currently, it is possible to define channel-based configuration 
variable using config-set BUT http_proxy configuration 
variable is not activated in this list of channel-based variable 
because at least PEAR/Command/Channels.php, 
PEAR/Command/Remote.php, PEAR/Downloader.php and 
PEAR/REST.php are not compliant with multiple proxies 
(channel-based proxies).

I request to have a channel-based http_proxy configuration 
variable as a new feature.

Test script:
---------------
In PEAR 1.8.1 distribution, I made following patches :

*** PEAR/Command/Channels.php
- Line 243 : $loc = $downloader->downloadHttp($channel, $this->ui, $tmpdir,null,null,false,$chan);
- Line 545 : $this->ui, $tmpdir, null, $lastmodified,false,$params[0]);
- Line 553 : $this->ui, $tmpdir, null, $lastmodified,false,$params[0]);
- Line 593 : $this->ui, $tmpdir, null, $lastmodified,false,$params[0]);

*** PEAR/Command/Remote.php
- Line 177 : '/channel.xml', $chan->lastModified(),null,null,null,false,$channel);

*** PEAR/Downloader.php
- Line 1585 : if ($config->get('http_proxy',null,$channel) &&
- Line 1586 : $proxy = parse_url($config->get('http_proxy',null,$channel))) {

*** PEAR/REST.php
- Line 315 : if ($this->config->get('http_proxy',null,$channel)&&
- Line 316 : $proxy = parse_url($this->config->get('http_proxy',null,$channel))


I am not sure this is a complete and bug-free patch but it works fine for me


Expected result:
----------------
Channel-based http_proxy configuration variable

Actual result:
--------------
Using proxy defined in http_proxy configuration variable for all 
channels and packages

PEAR: Bug 16187 [Open] Installer creates several pear.ini files

2009-05-05T19:07:25+00:00

PEAR Bug
Reported by runar0
2009-05-05T19:07:25+00:00
PHP: 5.2.9 OS: Windows Vista Package Version: 1.8.1

Description:
------------
I've noticed that PEAR keeps creating 
c:\php5\pear\{docs,data} folders even thought other paths 
were given to the go-pear script. After some testing I've been 
able to determin that the reason why this is happening is that 
in addition to creating a pear.ini file in the php directory (I 
changed the path manually during install) pear creates a 
aditional configuration file in c:\windows\ at the first call to 
either pear install or pear upgrade-all. This new configuration 
file has some of the paths that was given to go-pear, but 
settings such as data_dir and doc_dir are resetted to the 
default.

I've tried this several times, removing any trace of pear and 
using fresh php installations aswell as the lastest go-
pear.phar.

PEAR: Feature/Change Request 15909 [Open] Allow -f as short option when uninstalling a package

cweiske at php dot net — 2009-03-09T01:30:48+00:00

PEAR Feature/Change Request
Reported by cweiske
2009-02-18T11:36:43+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
   pear uninstall only accepts " --ignore-errors" to force the uninstallation, not "-f" as it is common for all other commands.

Test script:
---------------
      

Expected result:
----------------
      

Actual result:
--------------

PEAR: Feature/Change Request 15745 [Open] Global state vs test expectations (Packager tests)

daniel dot oconnor at gmail dot com — 2009-04-04T00:13:32+00:00

PEAR Feature/Change Request
Reported by doconnor
2009-01-23T20:41:40+00:00
PHP: 5.2.6 OS: Ubuntu 8.10 Package Version: CVS

Description:
------------
Packager unit tests fail for me - they produce the correct output; but also generate warnings.

This is because the user I'm running under doesn't have permission to write to the appropriate tmp folder, and remove certain folders.

The unit tests should be using the dummy configuration provided (tests/PEAR_Packager/setup.inc.php does this); but don't appear to be.

Workarounds:
 * Run the unit tests via sudo
 * Change my pear configuration (pear config-set temp_dir 123)


A good way to fix this long term would be to shift the PEAR Config fetching to the very start of the application, and pass it through to the appropriate layers, rather than a static method / singleton.

$pear->setConfig(new PEAR_Config());

Test script:
---------------
# Grab from CVS
cvs update -d && sudo pear install -f package2.xml

pear config-set temp_dir /some/path/you/dont/have/write/access/to

cd tests/
pear run-tests PEAR_Packager/test_warning.phpt

Expected result:
----------------
tests done

Actual result:
--------------
tests done
Warning: Could not open dir /tmp/hsperfdata_tomcat6 in /usr/share/php/System.php on line 99

Warning: Could not open dir /tmp/orbit-root in /usr/share/php/System.php on line 99

Warning: Could not open dir /tmp/hsperfdata_tomcat6 in /usr/share/php/System.php on line 99

Warning: Could not open dir /tmp/orbit-root in /usr/share/php/System.php on line 99

PEAR: Documentation Problem 15578 [Assigned] Need howto: offline installation

cweiske at php dot net — 2009-04-04T00:18:20+00:00

PEAR Documentation Problem
Reported by cweiske
2009-01-09T05:18:32+00:00
PHP: 5.2.8 OS:  Package Version: 1.7.2

Description:
------------
Sometimes you want to install pear without having internet access. There is no documentation how to do this - go-pear accesses cvs.php.net.

PEAR: Bug 15439 [Verified] Pear use through a proxy

progi1984 at gmail dot com — 2009-06-28T23:43:29+00:00

PEAR Bug
Reported by progi1984
2008-12-29T08:10:25+00:00
PHP: 5.1.6 OS: CentOS Package Version: 1.7.2

Description:
------------
When i have a username which contains an arobase, the pear command can't access to pear servers.

Test script:
---------------
# pear config-set http_proxy http://user@fai.fr.fto:password@ipproxy:portproxy
config-set succeeded
# pear list-all
Connection to `fai.fr.fto:password@ipproxy:portproxy' failed:

PEAR: Feature/Change Request 15098 [Open] Echo Task

ifeghali at php dot net — 2009-02-26T14:21:09+00:00

PEAR Feature/Change Request
Reported by ifeghali
2008-11-20T07:31:12+00:00
PHP: 5.2.6 OS:  Package Version: 1.7.2

Description:
------------
I would love to print some general information or even how did the installation gone (which files went where) when a package is installed. 

Some important stuff like command line tools and web front end can be installed without user's notice, if they don't take some time to read docs or release notes.

That could be avoided if package.xml could handle some dynamic echos after installing/upgrading. Maybe a post-install task that runs independent of the user's request ?

PEAR: Feature/Change Request 14842 [Open] check assigned memory rather than crashing due to memory_limit being exceeded

ken at linux dot ie — 2009-08-02T13:12:16+00:00

PEAR Feature/Change Request
Reported by kguest
2008-10-21T08:17:32+00:00
PHP: 5.2.5 OS: Windows Package Version: 1.7.2

Description:
------------
I installed version 1.7.4 of wamp and proceeded to upgrade pear from 1.6.1 to the current version.

Got a fatal error regarding memory_limit being too low - doubled it to 16MB and upgrade worked ok.


pear itself should check the assigned memory
when < 16MB, it should tell the user

#
C:\wamp\php>pear list
#
INSTALLED PACKAGES, CHANNEL PEAR.PHP.NET:
#
=========================================
#
PACKAGE          VERSION STATE
#
Archive_Tar      1.3.2   stable
#
Console_Getopt   1.2.3   stable
#
PEAR             1.6.1   stable
#
Structures_Graph 1.0.2   stable
#
 
#
C:\wamp\php>pear upgrade-all
#
Will upgrade channel://pear.php.net/pear
#
WARNING: channel "pear.php.net" has updated its protocols, use "channel-update p
#
ear.php.net" to update
#
Did not download optional dependencies: pear/XML_RPC, use --alldeps to download
#
automatically
#
pear/PEAR can optionally use package "pear/XML_RPC" (version >= 1.4.0)
#
downloading PEAR-1.7.2.tgz ...
#
Starting to download PEAR-1.7.2.tgz (302,744 bytes)
#
.....................done: 302,744 bytes
#
 
#
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 9
#
8304 bytes) in C:\wamp\php\PEAR\PEAR\PackageFile\Generator\v2.php on line 207

Test script:
---------------
http://pastebin.com/m250aefec

PEAR: Bug 14841 [Assigned] Installing pear into directory with space fails

cweiske at php dot net — 2009-02-10T15:10:31+00:00

PEAR Bug
Reported by cweiske
2008-10-21T07:16:26+00:00
PHP: Irrelevant OS:  Package Version: 1.7.2

Description:
------------
Installing pear freshly into a directory with spaces (e.g. on windows /Documents and settings/User name/) fails.

This could be an issue in System.php

PEAR: Bug 14387 [Open] pear config-create case problem

leonardo dot saracini at tiscali dot it — 2008-12-08T05:46:45+00:00

PEAR Bug
Reported by lesar
2008-07-22T11:34:17+00:00
PHP: 5.2.3 OS: ubuntu 7.10 Package Version: 1.7.2

Description:
------------
if you type at prompt
pear config-create ....
all the path are in lower case.
if you have a path /var/www/user/pear/PEAR/...
config-create write /var/www/user/pear/pear/...

PEAR: Bug 14234 [Open] list-all and remote-list does'nt show all packages

progeja at gmail dot com — 2008-06-25T05:48:12+00:00

PEAR Bug
Reported by progeja
2008-06-25T05:48:12+00:00
PHP: 5.2.5 OS: Windows XP Package Version: 1.7.2

Description:
------------
I have xampp (1.6.6a) installation in my Windows XP SP3 pc.

I disabled xampp pear installation and created clean pear installation. After installing when I try get list all packages from pear server I get only few (16 packages + allready installed ones)

When I try search packages everything works fine.

My pear config:

----------------------
C:\srv\www>pear config-show
CONFIGURATION (CHANNEL PEAR.PHP.NET):
=====================================
Auto-discover new Channels     auto_discover    
Default Channel                default_channel  pear.php.net
HTTP Proxy Server Address      http_proxy       
PEAR server [DEPRECATED]       master_server    pear.php.net
Default Channel Mirror         preferred_mirror pear.php.net
Remote Configuration File      remote_config    
PEAR executables directory     bin_dir          C:\DEV\PEAR
PEAR documentation directory   doc_dir          C:\DEV\PEAR\pear\docs
PHP extension directory        ext_dir          C:\srv\xampp\php\ext\
PEAR directory                 php_dir          C:\DEV\PEAR\pear
PEAR Installer cache directory cache_dir        C:\DOCUME~1\userg\LOCALS~1\Temp\pear\cache
PEAR configuration file        cfg_dir          C:\php5\pear\cfg
directory
PEAR data directory            data_dir         C:\DEV\PEAR\pear\data
PEAR Installer download        download_dir     C:\DOCUME~1\userg\LOCALS~1\Temp\pear\download
directory
PHP CLI/CGI binary             php_bin          C:\srv\xampp\php\php.exe
php.ini location               php_ini          
PEAR Installer temp directory  temp_dir         C:\DOCUME~1\userg\LOCALS~1\Temp\pear\temp
PEAR test directory            test_dir         C:\DEV\PEAR\pear\tests
PEAR www files directory       www_dir          C:\php5\pear\www
Cache TimeToLive               cache_ttl        3600
Preferred Package State        preferred_state  beta
Unix file mask                 umask            0
Debug Log Level                verbose          1
PEAR password (for             password         
maintainers)
Signature Handling Program     sig_bin          c:\gnupg\gpg.exe
Signature Key Directory        sig_keydir       C:\DEV\PEAR\pearkeys
Signature Key Id               sig_keyid        
Package Signature Type         sig_type         gpg
PEAR username (for             username         
maintainers)
User Configuration File        Filename         C:\DEV\PEAR\pear.ini
System Configuration File      Filename         C:\DEV\PEAR\pearsys.ini
-------------------------------------


Test script:
---------------
C:\srv\www>pear list-all

Actual result:
--------------
ALL PACKAGES [CHANNEL PEAR.PHP.NET]:
====================================
PACKAGE                  LATEST  LOCAL
pear/Benchmark           1.2.7
pear/Config              1.10.11 1.10.11
pear/Gtk_VarDump         1.0.0
pear/Gtk_ScrollingLabel  1.0.0
pear/Gtk_FileDrop        1.0.2
pear/Gtk_Styled          1.0.0
be controlled by the programmer.
pear/Log                 1.11.0
pear/Numbers_Roman       1.0.2
pear/Numbers_Words       0.15.0
pear/FSM                 1.3.0
pear/QA_Peardoc_Coverage 1.1.1
pear/Science_Chemistry   1.1.0
pear/Services_Akismet
pear/Stream_SHM          1.0.0
pear/Stream_Var          1.0.0
pear/VersionControl_SVN  0.3.1
pear/Archive_Tar                 1.3.2
pear/Console_Getopt              1.2.3
pear/MIME_Type                   1.0.0
pear/PEAR                        1.7.2
pear/Structures_Graph            1.0.2
pear/XML_Parser                  1.2.8
pear/XML_Serializer              0.18.0
res and vice versa.
pear/XML_Util                    1.1.4

PEAR: Feature/Change Request 13648 [Open] Add SVN feature to pear/pecl command

philip at roshambo dot org — 2009-08-09T17:39:04+00:00

PEAR Feature/Change Request
Reported by philip
2008-04-10T18:24:29+00:00
PHP: 5_3 CVS-2008-03-16 OS: Mac Package Version: CVS

Description:
------------
This feature request adds a "cvs type" to both pear and pecl commands. So for example:

$ pecl install foo-cvs

This would download pecl/foo from CVS and build it.

Test script:
---------------
It might do something like:

rm -rf fooTemp

cvs -d :pserver:cvsread:phpfi@cvs.php.net:/repository login
cvs -d :pserver:cvsread:@cvs.php.net:/repository checkout -d fooTemp pecl/foo

cd fooTemp
phpize
./configure
make
...

PEAR: Documentation Problem 13563 [Assigned] Unattendet installation documentation

cweiske at php dot net — 2008-05-13T02:23:24+00:00

PEAR Documentation Problem
Reported by cweiske
2008-04-02T06:50:35+00:00
PHP: 5.2.5 OS:  Package Version: 1.7.1

Description:
------------
The phar install package has options which allow an unattendet installation of PEAR (without user input). This should be documented in the manual.

PEAR: Feature/Change Request 13346 [Open] Add uninstall option to follow dependencies

pear at timj dot co dot uk — 2008-04-11T07:14:50+00:00

PEAR Feature/Change Request
Reported by timj
2008-03-08T15:18:40+00:00
PHP: Irrelevant OS:  Package Version: 1.7.1

Description:
------------
It would be nice if "pear uninstall" had an option to uninstall all the dependencies which required the package you are uninstalling, instead of just failing or requiring the user to manually follow the dependency tree. 

A nice name for this might be "--alldeps"

Test script:
---------------
Assume package "Bar" depends on package "Foo".

pear uninstall --alldeps Foo

Expected result:
----------------
Foo and Bar are both uninstalled

PEAR: Feature/Change Request 13256 [Open] Add option to prevent installation of documentation

pear at timj dot co dot uk — 2008-02-28T13:56:14+00:00

PEAR Feature/Change Request
Reported by timj
2008-02-28T13:56:14+00:00
PHP: Irrelevant OS:  Package Version: 1.7.1

Description:
------------
It is possible that a piece of software packaged using the PEAR installer might have a large amount of documentation packaged with it.

Whilst this is useful for development, it is often at least useless and at worst a hindrance on a live server, where minimising disk space usage may be a serious concern.

Therefore a "--skip-docs" or similar option to "pear install" would be really handy. For comparison, a similar thing exists in the RPM world (--excludedocs)

PEAR: Feature/Change Request 13186 [Open] sign when packaging

cweiske at php dot net — 2008-02-24T03:08:44+00:00

PEAR Feature/Change Request
Reported by cweiske
2008-02-24T03:08:44+00:00
PHP: 5.2.5 OS:  Package Version: 1.7.1

Description:
------------
This patch adds a --sign parameter to the package command. I moved the signature creation code out of the sign command into the packager.
The package file generator was modified to be able to add the signature to the file without extracting and re-compressing the archive

PEAR: Feature/Change Request 12898 [Open] Multiple instances of PEAR will cause conflicts and side effects

mega-squall at caramail dot com — 2008-01-13T21:10:28+00:00

PEAR Feature/Change Request
Reported by megasquall
2008-01-13T21:10:28+00:00
PHP: Irrelevant OS: Windows XP Package Version: 1.6.2

Description:
------------
When having installed several instances of PEAR, there are side effects using them in the same environment.

The first instance of PEAR run will populate environment varaibles with its values. Then it is needed to unset those variables prior to using any other instance of PEAR, or open another command line window.

Failing to do so will usually result in mixing things from two PHP versions. Considering that the first run version is php4 and the version which is intended to be called after is php5, it will result in using :

php4\php.exe
php4\pear\*
php5\php.ini
php5\*.dll

I think those values should be moved from environment variables to pear.ini

Test script:
---------------
# Batch file

cd \php4\
pear list

cd \php5\
pear list

Expected result:
----------------
INSTALLED PACKAGES, CHANNEL PEAR.PHP.NET:
=========================================
PACKAGE          VERSION STATE
...              ...     ...

INSTALLED PACKAGES, CHANNEL PEAR.PHP.NET:
=========================================
PACKAGE          VERSION STATE
...              ...     ...

Actual result:
--------------
INSTALLED PACKAGES, CHANNEL PEAR.PHP.NET:
=========================================
PACKAGE          VERSION STATE
...              ...     ...

" This application has failed to start because php4ts.dll was not found. Re-installing the application may fix this problem "

PEAR: Feature/Change Request 12815 [Open] PEAR::loadExtension($ext) generates an E_WARNING

rosier at interstroom dot nl — 2008-01-07T03:49:41+00:00

PEAR Feature/Change Request
Reported by rosier
2008-01-03T11:20:47+00:00
PHP: Irrelevant OS: Linux Package Version: 1.6.2

Description:
------------
I use an custom error handler and get the following error:

E_WARNING dl(): Unable to load dynamic library '/path/to/php_mysql.so'

This error is generated because there are 2 dl() calls in PEAR::loadExtension($ext). The first call generates the E_WARNING. The second call loads the library.

I added an patch that does only one dl() call.

PEAR: Feature/Change Request 11641 [Open] Poor reporting of conflicting requirements

pear at timj dot co dot uk — 2008-04-09T17:14:55+00:00

PEAR Feature/Change Request
Reported by timj
2007-07-19T04:52:37+00:00
PHP: Irrelevant OS:  Package Version: 1.6.1

Description:
------------
If I have the following packages:

package X
requires "Foo_Bar", no recommended version
requires Y

package Y
requires "Foo_Bar", recommended version 1.0.0

and Foo_Bar exists as both v1.0.0 and 1.0.1 on the channel server, then an attempt to install X via "pear install" results in a failure with the error:

Duplicate package channel://whatever/Foo_Bar-1.0.1 found
Duplicate package channel://whatever/Foo_Bar-1.0.0 found

Now, ignoring the fact that I'm not sure a failure here is the right behaviour (arguably there is a separate bug here: installing either 1.0.0 or 1.0.1 would fully satisfy the deps in either case albeit requiring a warning), the reporting is unhelpful as it does not specify:

a) which packages in the dependency chain required 1.0.0 and which required 1.0.1

b) whether those requirements were implicit or explicit.

I would suggest that a better output would look something like this:

Conflicting requirements for package "Foo_Bar":
 - X requires Foo_Bar; latest version in channel is 1.0.1
 - Y requires Foo_Bar; recommended version is 1.0.0

PEAR: Feature/Change Request 11213 [Open] Portage-like USE flags to automatically install optional dependencies

is_null at devangels dot org — 2007-06-06T11:16:12+00:00

PEAR Feature/Change Request
Reported by isnull
2007-06-03T02:55:19+00:00
PHP: Irrelevant OS: Irrevelant Package Version: 1.5.4

Description:
------------
PEAR CLI could use a system similar to portage with optionnal packages.

If you don't know what is portage, i'll try to explain :
* package foo has optionnal dependency : bar
* if foo is installed with USE flag 'bar', bar is installed along with foo
* if foo is installed with USE flag '-bar', foo is installed without bar
* USE could be used like USE='bar' pear install --pretend foo
* USE could be setup in a global USE configuration, or locally with a per-package USE flag list

Example, sysadmin might install foo with bar :
# USE="bar" pear install --pretend foo
Sysadmin agrees, sets bar to foo (locally)
# echo "foo bar" >> /etc/pear/package.use
Sysadmin installs foo with bar :
# pear install foo

Other example, sysadmin thinks that all packages should have 'bar' USE flag, adds it to a global USE, or to a profile.
Then, sysadmin doesn't want 'bar1' in foo : 
# echo "foo bar -bar1" >> /etc/pear/package.use

Finally, default USE flags could be setup in profiles, for example a server profile that would set -gtk, a cli profile that would set -web to PEAR (web would trigger install of the pear web frontend).

Also, there could be keywords, like alpha or stable.
Sysadmin wants to check what dependencies for alpha package foo :
# ACCEPT_KEYWORDS="alpha" pear install --pretend foo
Again, keywords could be set up in profile, globally or localy.

PEAR: Feature/Change Request 11195 [Open] Install required deps by default after asking

jeichorn at JoshuaEichorn dot com — 2008-07-12T09:36:01+00:00

PEAR Feature/Change Request
Reported by jeichorn
2007-05-31T16:47:48+00:00
PHP: 5.2.1 OS:  Package Version: CVS

Description:
------------
pear install package 
by default should show you if any deps are required and after asking you automatically install them

Look at what yum does for an example

PEAR: Feature/Change Request 11190 [Open] Allow full Boolean operators for Dependancies

cipri at php dot net — 2007-05-31T14:55:10+00:00

PEAR Feature/Change Request
Reported by cipri
2007-05-31T14:55:10+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 1.5.4

Description:
------------
It would be great if we could use boolean operators to define Dependancies, ie:

Require PHP 5.2.2 OR PEAR::PHP_Compat >= 1.2.0
Require PEAR >= 1.6.0 || ! PHP 5.2.1

PEAR: Feature/Change Request 11117 [Open] Add pre-install scripts that can veto install

development at domain51 dot com — 2007-05-25T23:41:56+00:00

PEAR Feature/Change Request
Reported by tswicegood
2007-05-23T17:25:51+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
Having the ability to add a script that runs before an install gives the packager flexibility to do prep and/or dependency checking before the package is installed.  If the script(s) could be given the ability to veto the installation, they could allow for dependencies outside of PHP.

Other possible uses for this script include:
* Registration of product(s) to allow to use
* Checking of licenses for proprietary software installs

As mentioned with the postinstall tasks, there is a security issue inherent in allowing execution of scripts.  The obvious way to address this is to prompt the user prior to running the scripts unless they install with --force.  The prompt could ask to execute the script, proceed without executing it (if its optional), view the install script, or abort.

PEAR: Feature/Change Request 11101 [Open] Automatic creation of bundles (package + dependencies)

saschagros at bluewin dot ch — 2007-05-23T02:49:28+00:00

PEAR Feature/Change Request
Reported by berdir
2007-05-23T02:49:28+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 1.5.4

Description:
------------
It would be great if Pyrus could automatically create a bundle of a package. This would include all direct and indirect dependencies.

I am doing this by hand, because such a bundle has some advantages:

- Speed: I have an application with 40 dependencies (direct and indirect), install/upgrade with bundle takes a few seconds, with a normal package multiple minutes.

- Flexibility: Installation is possible everywhere and everytime. For example on servers without direct internet access and even if pear.php.net is down.

- Security: You can be sure that you have all dependencies (PHPUnit2-problem) and that they are the same on every installation.

PEAR: Feature/Change Request 10765 [Open] check signature when installing/upgrading files

cweiske at php dot net — 2007-06-01T11:11:32+00:00

PEAR Feature/Change Request
Reported by cweiske
2007-04-18T02:32:32+00:00
PHP: 5.2.1 OS:  Package Version: 1.5.2

Description:
------------
If a package contains a package.sig file, it should be used to verify the validity of the package. Currently, you can sign a package, that signature is used nowhere.

PEAR: Feature/Change Request 10671 [Open] Default minimal validation for package.xml

pear at timj dot co dot uk — 2007-04-17T16:27:53+00:00

PEAR Feature/Change Request
Reported by timj
2007-04-09T15:03:41+00:00
PHP: Irrelevant OS:  Package Version: CVS

Description:
------------
This is a PEAR2 thing. I believe that everything in this bug can already be achieved with PEAR 1.4 and a custom validation package; this feature request is purely about:

a) shipping an additional, minimal validator
b) making it the default

Considering the PEAR Installer separately from PEAR the set of packages, the *default* validation done on a package.xml file should be as minimal as possible, with more strict requirements being enforced for packages in the PEAR channel, rather than the other way round as at present.  The purpose of this is:

- to distinguish between "content" and "policy". The former is objective, the latter subjective. "content" means describing intrinsic things about the content, like the version number. "policy" means things like "you really ought to have a description"
- to save duplication of metadata between packages and other systems
- to keep package.xml files as simple as possible
- to ease the learning curve for developers who are new to the PEAR Installer
- to make writing documentation for beginners easier, allowing the explanation of "essential" concepts separate from "nice to haves".

By "minimal" I mean the minimal set of metadata which:

- accurately and unambiguously describes a package
- enables the deployment process to take place

This should take into account that the PEAR Installer may be used in small teams in private environments, where non-essential metadata may already be maintained outside of the package deployment system, and inclusion in it is therefore unnecessary duplication. ("content" vs "policy" again)

I will attach a sample package.xml which I would suggest is "minimal" for the purposes of this bug. However, just to discuss some of the currently-required tags that I would propose removing in more detail:

-  - this is a descriptive tag which is nothing to do with the deployment process and is metadata which is likely maintained elsewhere (particularly if you are running a database-driven channel server)

-  - this is purely descriptive and often held elsewhere

-  - the API has less meaning in the context of an application than it does for a library, and it may already be implied by the package version where a policy on API changes exists.

-  - whilst this should "probably" be present in most cases, again in a small team environment it may be superfluous as the  is probably enough to enable ready identification of a package, with full description/docs held elsewhere

-  - again, this is purely descriptive

-  - this should default to 1.

I must re-emphasise that I am ***NOT*** saying that the above tags are not useful, just that they are not necessary in all environments and therefore shouldn't be *required* by default. 

One possible one which I'm not sure about is:

-  - often, this is implied from the package/API versions where a policy on those is in place.

PEAR: Feature/Change Request 10667 [Assigned] Allow dependencies on API

pear at timj dot co dot uk — 2009-03-26T21:57:11+00:00

PEAR Feature/Change Request
Reported by timj
2007-04-09T14:10:21+00:00
PHP: Irrelevant OS:  Package Version: CVS

Description:
------------
This is a PEAR2 thing, probably.

It seems rather a shame that although we have an  version tag in package.xml, you can't use it as a dependency. In some ways, *IF* this is being used properly, it would make more sense than a package version dependency. Certainly this is true in some circumstances.

Therefore, PEAR2 should perhaps support a dep something like this:


  
    Foo_Bar
    1.0.0
    1.0.2
    1.0.1
  


(the implicit default "type" attribute for , etc. would be "packagever" or something)

PEAR: Feature/Change Request 10663 [Assigned] run-tests to accept " -d inisetting=xxx" option

techtonik at php dot net — 2007-08-16T14:29:14+00:00

PEAR Feature/Change Request
Reported by techtonik
2007-04-09T04:15:24+00:00
PHP: 4.4.4 OS:  Package Version: 1.5.2

Description:
------------
RFE to transparently pass php options through run-tests subcommand.

Now:
run-tests -i " -d inioption=value"

Needed:
run-tests -d inioption=value



Test script:
---------------
$ ../../bin/pear help run-tests


Expected result:
----------------
pear run-tests [options] [testfile|dir ...]
Run regression tests with PHP's regression testing script (run-tests.php).
Options:
  -r, --recur
        Run tests in child directories, recursively.  4 dirs deep maximum
  -d setting=blah
        ini settings to pass to php
  -l, --realtimelog
        Log test runs/results as they are run
  -q, --quiet
        Only display detail for failed tests
  -s, --simple
        Display simple output for all tests
  -p, --package
        Treat parameters as installed packages from which to run tests
  -u, --phpunit
        Search parameters for AllTests.php, and use that to run phpunit-based tests
  -t, --tapoutput
        Output run-tests.log in TAP-compliant format
  -c PHPCGI, --cgi=PHPCGI
        CGI php executable (needed for tests with POST/GET section)


Actual result:
--------------
pear run-tests [options] [testfile|dir ...]
Run regression tests with PHP's regression testing script (run-tests.php).
Options:
  -r, --recur
        Run tests in child directories, recursively.  4 dirs deep maximum
  -i SETTINGS, --ini=SETTINGS
        actual string of settings to pass to php in format " -d setting=blah"
  -l, --realtimelog
        Log test runs/results as they are run
  -q, --quiet
        Only display detail for failed tests
  -s, --simple
        Display simple output for all tests
  -p, --package
        Treat parameters as installed packages from which to run tests
  -u, --phpunit
        Search parameters for AllTests.php, and use that to run phpunit-based tests
  -t, --tapoutput
        Output run-tests.log in TAP-compliant format
  -c PHPCGI, --cgi=PHPCGI
        CGI php executable (needed for tests with POST/GET section)

PEAR: Feature/Change Request 10646 [Open] sign automatically when packaging if gnupg key set

cweiske at php dot net — 2007-04-18T05:22:42+00:00

PEAR Feature/Change Request
Reported by cweiske
2007-04-07T02:32:00+00:00
PHP: 5.2.1 OS:  Package Version: CVS

Description:
------------
It would be nice if the package would be signed automatically if I type "pear package" and have a gnupg key set in pear config.

PEAR: Feature/Change Request 10626 [Open] check writability of pear directories

cweiske at php dot net — 2008-07-12T09:50:35+00:00

PEAR Feature/Change Request
Reported by cweiske
2007-04-05T08:56:35+00:00
PHP: 5.2.1 OS:  Package Version: 1.5.1

Description:
------------
Sometimes you have a weird setup and some or all of your pear directories (php_dir, download_dir, ..) are not writable. It would be nice if pear had a status command which checked this and told you where the problems are.

PEAR: Feature/Change Request 10570 [Open] add ability to hold/freeze a package

mike at php dot net — 2007-03-31T00:11:02+00:00

PEAR Feature/Change Request
Reported by mike
2007-03-31T00:11:02+00:00
PHP: Irrelevant OS:  Package Version: CVS

Description:
------------
Ig uess something for v2.

IT would be nice if there was a feature like dpkg's hold status, that is, a package in "hold" status cannot be upgraded, removed etc.

eg:
$ pear hold Net_NTTP
> Status of Net_NTTP set to hold. Installed version is 1.0.1 stable.
$ pear upgrade-all
> Upgrading ...
> Not going to upgrade Net_NTTP because its status is set to hold.
> ...

Not sure of the command name though, maybe freeze/unfreeze would be better?

PEAR: Feature/Change Request 10524 [Analyzed] improve the efficiency of REST for list-all/list-upgrades/remote-list

greg at chiaraquartet dot net — 2009-08-11T21:05:05+00:00

PEAR Feature/Change Request
Reported by cellog
2007-03-27T10:15:36+00:00
PHP: Irrelevant OS: n/a Package Version: 1.5.1

Description:
------------
as referenced by Tias Guns in pear-dev:

http://news.php.net/php.pear.dev/46043

REST could use some efficiency boosts on the client-side and the server-side as well.

PEAR: Feature/Change Request 10413 [Open] Relative paths in registry etc.

jan at horde dot org — 2007-03-19T06:43:42+00:00

PEAR Feature/Change Request
Reported by yunosh
2007-03-19T06:43:42+00:00
PHP: Irrelevant OS:  Package Version: CVS

Description:
------------
This is a feature request for PEAR 2.0.

The goal is to bundle a PEAR respository including installer out of the box. At the moment, if you bundle a set of PEAR packages with your application, it's complicated to allow updgrading of these packages without having to upgrade the whole application. If all paths in a repository were relative, this would be much easier, and would also allow to move a repository to a different path without any problems.

PEAR: Feature/Change Request 10390 [Open] provide a simple way to manage parent/child PEAR installations

greg at chiaraquartet dot net — 2007-03-15T10:02:48+00:00

PEAR Feature/Change Request
Reported by cellog
2007-03-15T10:02:43+00:00
PHP: Irrelevant OS: n/a Package Version: CVS

Description:
------------
When implementing cascading registries, it would be very important for breakage reasons to also allow a reverse cascade, so that the parent registry can determine whether an upgrade would break a child registry installation.  This way, the child registries would not have to be protected from a bad upgrade by the parent registry.

PEAR: Feature/Change Request 4208 [Open] Add ability to migrate a package to another channel

cellog at php dot net — 2009-03-27T00:05:00+00:00

PEAR Feature/Change Request
Reported by cellog
2005-04-22T18:42:05+00:00
PHP: Irrelevant OS: n/a Package Version: 

Description:
------------
Currently, once a package is in a channel, it is stuck.  This means if you ever move it to another channel, you have to use --ignore-errors to install it because it will conflict with the package from the other channel.

Security is an issue, so the only way to do this is to have the specification in the old channel's final release, as in:

Chiara_PEAR_Server
pear.chiaraquartet.net

 PEAR_Server
 pear.php.net


This would be the top of Chiara_PEAR_Server's final release at pear.chiaraquartet.net.  The releases at pear.php.net would then be able to upgrade from the older Chiara_PEAR_Server with no penalty.

This is most useful for a package that retains the same name.  The example above is moot, because a Chiara_PEAR_Server package would not conflict with a PEAR_Server because all the files are in Chiara/