Description: ------------ As nobody reply yet to my help request on pear-dev mailing list (posted on Jan 9, 2007) I'll fill this bug report. I suppose its a bug. Don't hurt me if its not, but as I've followed instructions available on PEAR manual [1], I don't see where is the problem. [1] http://pear.php.net/manual/en/installation.shared.php#installation.shared.ftp Resume of my platform test: - Windows XP SP2 - PHP 5.2.0 - a fresh install of PEAR 1.5.0RC3 with go-pear.phar, that installed me first : Archive_Tar 1.3.2 stable Console_Getopt 1.2 stable PEAR 1.4.11 stable - PEAR_RemoteInstaller 0.3.1 Related to PEAR manual, I've changed some real config-name, but its look like : - Full path to my remote home directory /home/username/ this is directory where I'm FTP connected - Full path to my public web dir /home/username/www - Full path where I've decided to install PEAR /home/username/inc * Creating customized config file for both the local and the remote host, gave me : C:\remote\pear\pear.ini C:\remote\pear\ pear -c pear.ini config-create /home/username/inc .pearrc Local config (pear.ini) resume : bin_dir C:\remote\pear doc_dir C:\remote\pear\pear\docs ext_dir c:\wamp\php\ext\ php_dir C:\remote\pear\pear cache_dir C:\remote\pear\pear\cache data_dir C:\remote\pear\pear\data download_dir C:\remote\pear\pear\temp php_bin C:\wamp\php\php.exe temp_dir C:\remote\pear\pear\temp test_dir C:\remote\pear\pear\tests Remote config (.pearrc) resume : bin_dir /home/username/inc doc_dir /home/username/inc/pear/docs ext_dir c:\wamp\php\ext php_dir /home/username/inc/pear cache_dir /home/username/inc/pear/cache data_dir /home/username/inc/pear/data download_dir /home/username/inc/pear/temp php_bin C:\wamp\php\php.exe temp_dir /home/username/inc/pear/temp test_dir /home/username/inc/pear/tests * Setting remote_config to : ftps://user:password@host/.pearrc or ftp://user:password@host/.pearrc FTP secure (open ssl) or unsecure gave me same results With .pearrc uploaded to: /home/username/.pearrc * NOW synchronize package operation: C:\remote\pear\ pear -c pear.ini remote-install C:\path_to_pear_packages\HTML_Common-1.2.3.tgz install ok: channel://pear.php.net/HTML_Common-1.2.3 Could not open remote file ftps://user:password@host/home/username/inc/pear/HTML/Common.php for saving a copy of local file C:\remote\pear\pear\HTML\Common.php remote install failed: channel://pear.php.net/HTML_Common-1.2.3 Of Course HTML_Common as no task replacement, but HTML_Quickform_advmultiselect 1.3.1 (aka QFAMS) as many, and I got same error. BTW, if i decide to change .pearrc config and remove /home/username prefix : bin_dir /inc doc_dir /inc/pear/docs ext_dir c:\wamp\php\ext php_dir /inc/pear cache_dir /inc/pear/cache data_dir /inc/pear/data download_dir /inc/pear/temp php_bin C:\wamp\php\php.exe temp_dir /inc/pear/temp test_dir /inc/pear/tests And set remote_config to : ftps://user:password@host/inc/.pearrc or ftp://user:password@host/inc/.pearrc With an upload copy of local .pearrc to /home/username/inc I got no error with packages that have no task replacements (such as HTML_Common), but others (QFAMS) still gave me errors. So Where is the problem, and what shall I DO ? Expected result: ---------------- All packages (with or without tasks replacement) uploaded to remote host (full synchronize local to remote) Actual result: -------------- Depending of config choice, only package without tasks replacement can be upload to remote host.

this doesn't seem to be a problem with replacements, but instead with creating subdirectories, as replacements have no effect on any portion of the remote installation process (they simply don't exist in the installed package registry any longer, and remote installation only uses the registry, not the package.xml). Could you try creating a package with no replacements that has subdirectories that need to be created? It may in fact be a problem with the ftp extension on your PHP version, as I've heard of a LOT of problems with various things in the ftp stream implementation. You might also try the same packages with PHP 5.2.1 and see if there is any improvement. If so, I will bump the minimum PHP version in package.xml