Re: [pear-webmaster] Fwd: [PEAR] [ANNOUNCEMENT] pearweb-1.26.0 (stable) Released.

[email protected] (Brett Bieber) Tue, 10 Apr 2012 12:59:31 -0500
Newsgroups php.pear.webmaster
Message-ID <CAF6z_LKA0O4FH=UxQrC6DXM9sGeJ07K+d-ShALPv0ZUkwWDYnA@mail.gmail.com>
On Tue, Apr 10, 2012 at 12:52 PM, Daniel O'Connor
<[email protected]>wrote:

> So... I pushed this out as a release and broke everything - sigh.
>
> Oddly, pear.php.net didn't list it as an upgrade when I did
> $ sudo -s
> $ pear upgrade pearweb
>
> I decided on a dry run - reinstalling the same version as is on the
> machine.
> $ pear upgrade -f pearweb-1.25.0
>
> Everything broke
> Annoyingly, the baseinstalldir in the package.xml and what's on
> pear.php.netare different - the code gets installed to
> /var/www/html/pearweb/
> pear.php.net/pear.php.net/
>
> This isn't at all like the test machine which behaves "normally" and sticks
> it where I think it should live
>
> I've had to
> $ cd /var/www/html/pearweb/pear.php.net/
> $ cp -R pear.php.net/* .
> ... in order to fix this.
>
> After a bit of mucking around; everything seems OK, I still can't get
> 1.26.0 to show up.
>
> I had to
> $ pear upgrade http://pear.php.net/direct/path/to/package
>
> Nothing broke this time, but the code still installed
> to /var/www/html/pearweb/pear.php.net/pear.php.net/
>
> However, the moment I copied all of the nested files
> $ cd /var/www/html/pearweb/pear.php.net/
> $ cp -R pear.php.net/* .
>
> ... everything broke again.
>
> Rather than try to figure it out with a broken site, I just went to the
> working 1.25.0 installation; and copied the two files I was interested in
> upgrading specifically (style.css, package-info.php).
>
> Can someone else with a dim understanding of how pearweb and pear are meant
> to be playing together check out pear config, pearweb's package.xml, etc
> and tell me what the hell I've missed?
>

There's a root cron job which should do this automatically for you —

/usr/bin/php -f /var/www/html/pearweb/pear.php.net/cron/update-website.php

When I perform manual updates to the system pear configuration, I always
use the config file in /root/.pearrc, and specify it with each command.

I usually run:
sudo pear -c /root/.pearrc ...

As long as the package is structured the same and you're using the right
config values, everything should work.

-- 
Brett Bieber