[whups] Yikes!

[Mike Baptiste]

Quoting Chuck Hagenbuch <chuck@horde.org>:

> Mike-
>
> This is the Whups list. There's a general horde list, and a dev list,
> both
> of which would be more appropriate forums for this thread.

I know - I posted here since I figured it might be user error and just
wanted to see if anyone else in whups world had seen this.  I know
developers hate 'it just broke' msgs on dev lists.  I had checked dev and
cvs and didn't see anything earth shattering.  I figured if I was really
stuck I'd post to dev.  But I was still digging.
>
> When you cvs update, do you include -d ?

Yes, well, I'm an idiot.  No - that was the problem.  The Cipher/blockmode
to BlockMode name change got me.  I learned a WHOLE lot about how horde
starts up though! :)  I finally traced it to that directory change (I hadn't
seen this email yet :( ) and a cvs update with -d pulled it in.  I had
forgotten to include -d by default.  Sigh.

The logging issue was interesting.  Turns out, I never restarted my browser
after the update (which was dumb now that I think about all the session mgmt
going on), so the old session info was being processed by horde and then it
hit Auth:: and died during the prefs factory setup - but without a peep (I
log E_ALL in PHP) I had to insert error_logs along the way to find where it
was hung.  When I restarted my browser and tried to login, I actually got an
error about blockmode not existing.  Then it was easy.  Not sure why it
wouldn't complain until then.

One thing I did note is after I updated all my PEAR modules to the latest
versions, test.php is giving me an error out of the File package:

Unknown error: Problem with method call - please report this bug
(/usr/local/lib/php/File.php:529)

Which is when it tries to unregister:

PEAR::registerShutdownFunc(array('File', '_File'));

I know this is more of a PEAR issue than horde.  But I figured I'd mention
it.  I can't see why it is complaining though - _File exists.  But I
digress....

Mike