Pear version warnings in PHP builds

LawsHosting

Verified User
Joined
Sep 13, 2008
Messages
2,372
Location
London UK
Code:
[PEAR] Archive_Tar    - upgraded:  1.4.9
[PEAR] Console_Getopt - already installed: 1.4.3
[PEAR] Structures_Graph- already installed: 1.1.1
pear/pear dependency package "pear/XML_Util" downloaded version 1.4.4 is not the recommended version 1.4.3, but may be compatible, use --force to install
pear/XML_Util cannot be installed, conflicts with installed packages
[PEAR] XML_Util       - upgraded:  1.4.4
pear/PEAR dependency package "pear/Archive_Tar" installed version 1.4.9 is not the recommended version 1.4.4, but may be compatible, use --force to install
pear/PEAR dependency package "pear/XML_Util" installed version 1.4.4 is not the recommended version 1.4.3, but may be compatible, use --force to install
[PEAR] PEAR           - upgraded:  1.10.11
Probably not, but, is this anything to worry about?

Also, as we disable php functions, I see these when building PHP
Code:
PHP Warning:  popen() has been disabled for security reasons in phar:///usr/local/directadmin/custombuild/php-7.3.17/pear/install-pear-nozlib.phar/OS/Guess.php on line 254
PHP Warning:  fgets() expects parameter 1 to be resource, null given in phar:///usr/local/directadmin/custombuild/php-7.3.17/pear/install-pear-nozlib.phar/OS/Guess.php on line 255
PHP Warning:  pclose() expects parameter 1 to be resource, null given in phar:///usr/local/directadmin/custombuild/php-7.3.17/pear/install-pear-nozlib.phar/OS/Guess.php on line 264
I understand it's pear stuff and nothing to do with CB.......
 
Also, why is https being used?
Code:
# ./build update
Could not get versions.txt from https://files.directadmin.com/services/custombuild.  Trying backup.
Ok, that worked.   Please try using a different mirror.
 
You might want to try searching before posting Peter. ;)
There is already a thread bout this.
 
Any reason why not https? It's a safer connection and good chance that if it not works it will change to http not sure about that.
But I see no reason why not to use https?
 
In that case you might check or refresh your browser or something. Because I visited before I reply'd previously and I had no isseus with invalid cert or dates and nothing fails in my browser.
 
Back
Top