Yes, we had the same problem on a few desktops that had a custom version.
I re-installed the custom version and excluded openoffice and oobasis from 
future sl-security updates.
Eve


On Wed, 16 Jun 2010, Simon Butcher wrote:

> Date: Wed, 16 Jun 2010 15:20:37 +0100
> From: Simon Butcher <[log in to unmask]>
> To: [log in to unmask]
> Subject: Problems caused by recent security update to openoffice.org-ure
>     package
> 
> hi everybody
>
> We run a lot of desktop SL machines running openoffice. Last week there was 
> an update to openoffice.org-ure package to 
> openoffice.org-ure-3.1.1-19.5.el5_5.1.i386
>
> As a result our 5.x machines with openoffice 2.3 have been suddenly upgraded 
> to 3.1 - a bit of a surprise!
>
> Unfortunately the update to openoffice.org-ure from sl-security broke the 
> custom OOo 3.0 we use on many of our desktops where the local custom repo was 
> not prioritized over sl-security repo (we provide newer versions of OOo 
> because only 2.3 was provided by the distro)
>
> i'm surprised that nobody else seems to be affected by this, or has mentioned 
> the jump to 3.1.
>
> we've now managed to put an emergency workaround in place. however, i'm just 
> writing this note in case others are affected.
>
> any "me too"s, or were most people using the old 2.3 OOo provided by SL5.x 
> (where x<5) ?
> -- 
> Simon Butcher
>
> Computer and IT Systems Manager
> School of Mathematical Sciences,
> Queen Mary, University of London,
> Mile End Road,
> London E1 4NS,
> United Kingdom.
>
> Telephone: +44 (0)20 7882 7348
>

***************************************************************
Eve Kovacs
Argonne National Laboratory,
Room E-217, Bldg. 362, HEP
9700 S. Cass Ave.
Argonne, IL 60439 USA
Phone: (630)-252-6208
Fax:   (630)-252-5047
email: [log in to unmask]
***************************************************************