pglock wrote:
I’ve been concerned about this for a while on my own server. I installed the
required Auth_SASL package using ‘pear install Auth_SASL’ as root. As a
check:
pear install Auth_SASL
Ignoring installed package pear/Auth_SASL
Nothing to install
I’ve modified php.ini to include /usr/local/bin/pear in the 'include_path’
so that the correct version of PEAR is picked up by the eGW
check_install.php script but it always reports the following:
Checking PEAR is installed: 1.6.2
Checking PEAR::Net_Socket is installed: 999.egw-pear
Checking PEAR::Auth_SASL is installed: False
PEAR::Auth_SASL is needed by: EMailAdmin, felamimail. You can install it by
running: pear install Auth_SASL
Checking PEAR::Net_IMAP is installed: 999.egw-pear
Checking PEAR::Net_Sieve is installed: 999.egw-pear
Checking PEAR::HTTP_WebDAV_Server is installed: 999.egw-pear
Checking PEAR::Log is installed: 999.egw-pear
So it looks as though the PEAR packages in egw-pear are detected ok but not
the Auth_SASL that I’ve manually installed.
Any ideas?
Yes, one:
Did you ever upgrade from php4 to php5 on your system? I have seen pear
report everything installed when there there were both pear and pear5
are installed on the system due to the php4-php5 upgrade that gave
similar errors. The reason was that both pear and pear5 pointed to the
same “/tmp/pear/cache…” file structure to keep track of what was
installed and while pear had "auth, imap, sasl, etc… " installed, pear5
did not but due to sharing the same cache structure when I went to
install any pear5 packages it would look at the /tmp/pear/cache files
and tell me it was already installed, but when egw went to look for
it, it wasn’t there.
See:
http://www.nabble.com/Upgraded-php4-to-php5-on-opensuse10.0---Pear-Errors--t4120787s3741.html
And you will see almost *EXACTLY* the problem you describe and how
painful it was for me to find out what the problem was.
Solution in that case: delete(or mv if you like) the /tmp/pear/cache
directory … and then install the needed pear packages … if that is
the problem it will work then. (if you’re curious and haven’t yet, take
a look, there is a ton of stuff under /tmp/pear/cache especially if you
have upgraded pear)
(This is solely from my experience on opensuse 10.0, your mileage may very)
–
David C. Rankin, J.D., P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
(936) 715-9333
(936) 715-9339 fax
www.rankinlawfirm.com
David C. Rankin wrote:
cindie wrote:
But they told me that Pear version is 1.6.2, it shoudn’t be Pear version
problem.
But I’m about to install it on a sub directory, would it cause any
problem?
further tips?
David C. Rankin wrote:
!YUuxc 44444444hrs5f4r wrote:
I’ve ask them to install PEAR Modules on my site. But when I run
installation
test I still got those warning information:
Checking PEAR::Auth_SASL is installed*: False*
PEAR::Auth_SASL is needed by: EMailAdmin, FeLaMiMail.* You can install
it
by
running:* pear install Auth_SASL
Warning Checking PEAR::Net_IMAP is installed*: False*
PEAR::Net_IMAP is needed by: FeLaMiMail.* You can install it by
running:*
pear install Net_IMAP
Warning Checking PEAR::Net_Sieve is installed*: False*
PEAR::Net_Sieve is needed by: FeLaMiMail.* You can install it by
running:*
pear install Net_Sieve
Warning Checking PEAR::HTTP_WebDAV_Server is installed*: False*
PEAR::HTTP_WebDAV_Server is needed by: Filemanager.* You can install it
by
running:* pear install HTTP_WebDAV_Server
Warning Checking PEAR::Log is installed*: False*
PEAR::Log is needed by: SyncML.* You can install it by running:* pear
install Log
any body help me out?
Tell them to see pear.hp.net and pay particular attention to:
[February 1, 2007] As of January 1, 2008, PEAR will be dropping support
for PEAR versions 1.3.6 and earlier. If you are using PEAR 1.3.6 or
earlier, we strongly encourage you to upgrade using these simple steps:
pear upgrade --force PEAR-1.3.6 Archive_Tar-1.3.1 Console_Get opt-1.2
pear upgrade --force PEAR-1.4.11
pear upgrade PEAR
The full story on what has changed, and what will change is here.
http://pear.php.net/news/package.xml.1.0.php
FIRST POINT
In this case, you don’t just need “ONE” pear, your the pear and the
proper components of pear installed. (In your case, you need 5 more
pears in your basket – see below) It may be true that they have the one
base pear package installed, but is sure doesn’t look line they have:
Checking PEAR::Auth_SASL is installed*: False*
Warning Checking PEAR::Net_IMAP is installed*: False*
Warning Checking PEAR::Net_Sieve is installed*: False*
Warning Checking PEAR::HTTP_WebDAV_Server is installed*: False*
Warning Checking PEAR::Log is installed*: False*
The pear Warning(s) are really really helpful. Call them back; send them
the errors; and tell them pay very close attention to the error messages
beginning each time they see an ‘* You can …’ in the error. I think
they can figure it out.
SECOND POINT
It doesn’t matter which directory you install egw in as long as you can
serve php documents out of it. Whether it is
http://documentroot/egroupware or
http://documentroot/subdir_1/subdir_2/egroupware. (I haven’t tried
this, but there is no logical reason why it would matter). If your
provider is nice, you can ask them to give you an Alias that says:
Alias /egroupware “/subdir_1/subdir_2/egroupware”
That way you can get to egroupware with http://yourdomain.com/egroupware
or on most commercially hosted sites I guess that would be
http://yourdomain.com/~cindie/egroupware
Good luck and have fun … and … remember it is always easier to run
your own server than try to explain to tech support what it is you need
them to do (If you can even get ahold of them)…
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft® Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
eGroupWare-users mailing list
eGroupWare-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-users
