Re: Problem with md5sums for LIVEUSER
| From: | MFriedman at symcor dot com | Date: | Tue, 28 Oct 2003 22:06:50 +0000 |
| Subject: | Re: Problem with md5sums for LIVEUSER | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-23095@lists.php.net to get a copy of this message | ||
I had been using:
PEAR 1.2.1 stable
When I upgraded I received the following message:
$ sudo /usr/local/apache/bin/pear upgrade PEAR
downloading PEAR-1.3b3.tgz ...
...done: 86,146 bytes
Optional dependencies:
'xmlrpc' PHP extension is not installed is recommended to utilize some
features.
sh: /usr/bin/cpp: No such file or directory
upgrade ok: PEAR 1.3b3
Oddly, XML_RPC was already installed. How does /usr/bin/cpp affect all of
this?
Hopefully my PEAR is not broken now. It seems ok.
Also, I uninstalled LiveUser and reinstalled using:
`$ /usr/local/apache/bin/pear install --ignore-errors
/home/mfriedman/LiveUser-0.9.tgz`
I got more md5sum errors. Same as before.
Thanks,
Matt.
Markus Wolff
<wolff@21st.de> To: MFriedman@symcor.com,
pear-dev@lists.php.net
cc:
28/10/2003 04:43 Subject: Re: [PEAR-DEV] Problem with md5sums for
LIVEUSER
PM
MFriedman@symcor.com wrote:
> Hi, when I do
pear install
> http://pear.php.net/get/LiveUser-0.9.tgz` I
> get:
>
> warning : bad md5sum for file
> /usr/local/apache/lib/php/LiveUser/LiveUser.php
> warning : bad md5sum for file
> /usr/local/apache/lib/php/doc/LiveUser/lgpl.txt
> warning : bad md5sum for file
> /usr/local/apache/lib/php/LiveUser/Perm/Container/DB_Complex.php
> and so on....
>
> The md5sum warnings aren't there when I try to install the previous
version
> of LiveUser.
Haven't had a problem like this yet. Which version of the PEAR
installer do you use? I have used 1.3b2 for making the package.
> Also, would anyone like to comment on how production ready the code is?
> I've been anxiously awaiting a "stable" release. Anyone using the
> application in it's current format?
IMHO, it is production-ready. It's been running stable for quite some
time now, it just had some features missing, some internal workings
have been rearranged and some minor API modifications have taken place
in the past - that's why it's still beta.
I guess a "real" 1.0 which is officially marked as "stable" will be
out before the end of this year. No huge changes are expected though,
just some minor additions and updated docs.
CU
Markus