Re: How to create the fake package to replace/remove/update packages

Ljubomir Ljubojevic <[email protected]> writes:

> I first run into problem when I wanted to easily replace old
> OpenOffice 2.x packages with OOO 3.1.1 buy adding Obsoletes: ~. into
> spec file, but I am not able to force yum do remove OpenOffice 2.x
> packages.

 I assume you have obsoletes processing turn on, on the clients? What
do you specfiles look like for the Obsoletes?

> Now OOO has changed packages from
>    ooobasis3.1-base-3.1.1-9420.x86_64.rpm
> to
>    ooobasis3.2-base-3.2.0-9483.x86_64.rpm
> (note the change in package name from 3.1 to 3.2, so there is no clear
> update path.

 Surely oobasis3.2 would obsolete oobasis3.1 ... no?

-- 
James Antill -- [email protected]